m13-domain-error

To design domain errors in Rust, use a layered taxonomy separating user-facing, internal, system, transient, and permanent errors. This approach maps business rules to technical error models, ensuring clear recovery strategies and observability across API services and background workers.

Categorizing transient and permanent errors in Rust involves distinguishing temporary failures like downstream timeouts from permanent ones like invalid input. This Skill provides a domain-aware taxonomy to classify errors, enabling appropriate recovery strategies such as retry or circuit breaker patterns.

Using thiserror and anyhow together in Rust allows you to define custom domain error types while easily propagating context. This Skill demonstrates how to map business rules using thiserror for structured errors and anyhow::Context for layered traceability from domain constraints to implementation.

You should apply a circuit breaker or retry pattern in Rust error handling when dealing with transient errors like downstream service failures. This Skill outlines recovery strategies including retry, fallback, and graceful degradation with practical Rust examples for robust service architecture.

Yes, you can use this domain error framework for a financial service in Rust. It provides guidance on separating user-facing messages from internal logs, categorizing errors from input validation to downstream service failures, and presenting actionable messages to users.