error-handling

Rust error-handling rules for choosing how programs report failures. Rust is a programming language; libraries are reusable code, while binaries are runnable programs.

In plain words
What is it for?
Use it when defining errors in Rust library crates or executable programs. It covers shared error definitions, error forwarding, added context, error chains, and documentation.
Why use it?
It prevents each part of a project from inventing a different error style. The rules make library errors structured and documented, while command-line programs can add useful context and user-facing messages.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/tyrchen/cursor-rust-rules/error-handling
Clone the repo
git clone --depth 1 https://github.com/tyrchen/cursor-rust-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,950 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02950
Opus 5 $0.00000 $0.01475
Sonnet 5 $0.00000 $0.00590
Haiku 4.5 $0.00000 $0.00295

Measured 2d ago against content hash 8ab864c6ff76, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

error-handling scanned grade A with 0 findings against 26 rules in 11 categories โ€” prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency โ€” measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/rust/quality/error-handling.mdc ยท 485 lines

How it starts

The opening of the file, as written. The whole thing โ€” 485 lines โ€” stays where its author put it; the contents beside it link to each section on GitHub.

๐Ÿšจ RUST ERROR HANDLING STANDARDS

TL;DR: Comprehensive error handling guidelines using thiserror for libraries and anyhow for binaries, with centralized error definitions per crate.

๐Ÿ” ERROR HANDLING STRATEGY SELECTION

graph TD
    Project["Project Analysis"] --> CrateType{"Crate Type?"}

    CrateType -->|"lib"| LibCrate["Library Crate"]
    CrateType -->|"bin"| BinCrate["Binary Crate"]

    LibCrate --> ThiserrorChoice["Use thiserror"]
    BinCrate --> AnyhowChoice["Use anyhow"]

    ThiserrorChoice --> LibFeatures["Library Features:"]
    AnyhowChoice --> BinFeatures["Binary Features:"]

    LibFeatures --> Structured["โ€ข Structured errors"]
    LibFeatures --> Derived["โ€ข Derive Error trait"]
    LibFeatures --> Transparent["โ€ข Error forwarding"]
    LibFeatures --> Documentation["โ€ข Error documentation"]

    BinFeatures --> Simple["โ€ข Simple error handling"]
    BinFeatures --> Context["โ€ข Rich context"]
    BinFeatures --> Chaining["โ€ข Error chaining"]
    BinFeatures --> EndUser["โ€ข End-user messages"]

    style Project fill:#4da6ff,stroke:#0066cc,color:white
    style CrateType fill:#ffa64d,stroke:#cc7a30,color:white
    style LibCrate fill:#4dbb5f,stroke:#36873f,color:white
    style BinCrate fill:#d94dbb,stroke:#a3378a,color:white

๐Ÿ“š LIBRARY CRATE ERROR HANDLING (thiserror)

Error Definition Pattern

// lib_crate/src/errors.rs
use thiserror::Error;

#[derive(Error, Debug)]
pub enum MyLibError {
    #[error("Invalid input: {message}")]
    InvalidInput { message: String },

    #[error("File not found: {path}")]
    FileNotFound { path: String },

    #[error("Permission denied")]
    PermissionDenied,

    #[error("Network error")]
    Network(#[from] reqwest::Error),

    #[error("IO error")]
    Io(#[from] std::io::Error),

    #[error("Parse error: {0}")]
    Parse(#[from] serde_json::Error),

    #[error("Configuration error: {message}")]
    Config { message: String },

    #[error("Internal error: {0}")]
    Internal(String),
}

// Additional result type alias for convenience
pub type Result<T> = std::result::Result<T, MyLibError>;

// Error construction helpers
impl MyLibError {
    pub fn invalid_input(message: impl Into<String>) -> Self {
        Self::InvalidInput {
            message: message.into(),
        }
    }

    pub fn file_not_found(path: impl Into<String>) -> Self {
        Self::FileNotFound {
            path: path.into(),
        }
    }

    pub fn config(message: impl Into<String>) -> Self {
        Self::Config {
            message: message.into(),
        }
    }

    pub fn internal(message: impl Into<String>) -> Self {
        Self::Internal(message.into())
    }
}

Read the full file on GitHub ยท 485 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen ยท 485 lines ยท 0 tokens per session scan A 8ab864c6ff76

Subscribe to this mod's changes

error-handling is a cursor rule published in the GitHub repository tyrchen/cursor-rust-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,950 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.