Does this skill help with HTTP status codes?

Yes, it includes guidelines for converting internal domain errors into meaningful HTTP status codes or CLI exit messages at the application boundary.

Why is unwrap() prohibited by this skill?

Prohibiting unwrap() and expect() ensures that all potential failure points are handled gracefully as Results, preventing unexpected runtime crashes.

When should I use thiserror over anyhow?

Use thiserror in library or domain code where callers need to match on specific error variants. Use anyhow in top-level application code for easy propagation and context.

Can I use anyhow in my public API?

This skill recommends against exposing anyhow::Error in public APIs. Public interfaces should use specific, typed errors defined via thiserror for better predictability.

Rust Error Handling (anyhow/thiserror)

Name: Rust Error Handling (anyhow/thiserror)
Author: See2et

bySee2et

•

API Development

Implements a robust error handling strategy by segregating domain-specific typed errors using thiserror and application-level context with anyhow.

About

This skill provides standardized guidance for architecting error propagation in Rust projects. It enforces a strict boundary between library/domain logic—where thiserror is used to define meaningful, typed errors—and application entry points (like main, CLI, or HTTP handlers), where anyhow is used for flexible error reporting and context enrichment. By prohibiting unwrap/expect and mandating context attachment, it ensures that your Rust applications are resilient, easier to debug, and provide helpful feedback to end-users.

Key Features

Enforces mandatory context attachment using .context() or .with_context()
Utilizes #[from] for automatic error conversion and source tracking
1 GitHub stars
Segregates thiserror for domain logic and anyhow for application boundaries
Prohibits unwrap() and expect() to prevent unexpected runtime panics
Provides patterns for converting internal errors to HTTP or CLI responses

Use Cases

Designing professional Rust libraries with stable, typed public Error APIs
Building web backends that require mapping domain errors to HTTP status codes
Developing CLI tools that need descriptive error messages and backtrace context

About

Key Features

Enforces mandatory context attachment using .context() or .with_context()
Utilizes #[from] for automatic error conversion and source tracking
1 GitHub stars
Segregates thiserror for domain logic and anyhow for application boundaries
Prohibits unwrap() and expect() to prevent unexpected runtime panics
Provides patterns for converting internal errors to HTTP or CLI responses

Use Cases

Designing professional Rust libraries with stable, typed public Error APIs
Building web backends that require mapping domain errors to HTTP status codes
Developing CLI tools that need descriptive error messages and backtrace context