m13-domain-error

Domain error handling strategies require classifying errors by audience, defining recovery patterns like retries and circuit breakers, and propagating context across users, developers, and operations. The skill guides you to structure typed error enums with retryability checks and ensure graceful degradation.

An error categorization matrix classifies domain-specific failures by target audience, recovery strategy, and example types. It works by mapping each error to a specific recovery pattern, ensuring failures are properly categorized, communicated, and recoverable across your service architecture.

Structuring an error hierarchy blueprint involves creating typed error enums that carry context and retryability checks. This blueprint organizes domain errors hierarchically, enabling services to programmatically determine whether to retry, fallback, or gracefully degrade when a failure occurs.

Classifying domain errors for a payment processing service involves categorizing failures by audience and recovery strategy, balancing user-facing messages, internal diagnostics, and operational alerts. The skill provides guidelines to structure these error types with appropriate retry policies and context propagation.

Circuit breakers and graceful degradation should be used when domain errors require resilience mechanisms to prevent cascading failures. The skill provides recovery pattern guidelines for applying retries, fallbacks, and circuit breakers based on the specific error type classification and retryability.

Yes, the skill explicitly designs error handling to categorize, recover, and communicate domain-specific failures across users, developers, and operations. It ensures errors are properly categorized and communicated by mapping each failure type to the appropriate audience and recovery strategy.