axum-errors-handling

What problem does it solve?

This Skill prevents incorrect or unsafe error handling in Axum by ensuring handlers and fallible middleware always produce valid HTTP responses with the right status codes and without leaking internal error details.

Core Features & Use Cases

• Type-system driven error responses: converts handler failures into responses by requiring Result<T, E> where E: IntoResponse, avoiding unwrap/expect/panic in request paths.
• Structured and safe error modeling: builds an AppError enum with IntoResponse plus From impls (optionally using thiserror), mapping known failures to distinct status codes like 404 and 422.
• Fallback and middleware adaptation: uses an anyhow catch-all pattern via a local newtype to keep orphan rules intact, and applies HandleError / HandleErrorLayer for fallible tower::Service middleware such as timeouts.

Quick Start

Use this skill to design an AppError enum and implement IntoResponse and From so your Axum handler can safely use the ? operator and return the correct status and client-safe body.