Implement Robust Error Handling Patterns

A skill for building resilient applications through robust error-handling strategies: gracefully handling failures, providing clear debugging context, and designing error-resilient APIs. It covers retry and circuit breaker patterns for transient failures, strategies for async and concurrent error handling, and techniques for making error messages genuinely useful to both end users and developers rather than opaque stack traces.

Use when implementing error handling in a new feature, designing an error-resilient API, debugging a production reliability issue, improving an application's fault tolerance, or building retry and circuit-breaker logic into a distributed system. Not for tasks unrelated to error handling - it explicitly stays out of scope for other domains, and it is not itself a debugging tool for a specific incident, so pair it with an incident-investigation skill for that.

Input is the failure scenario or API surface that needs resilient error handling - a new feature, an unreliable external dependency, or a distributed call chain. Output is an error-handling design: retry and circuit-breaker configuration, structured error messages tailored to their audience, and a resilience strategy for async or concurrent failure modes. For detailed patterns and worked examples, it points to resources/implementation-playbook.md.

References its own companion resource, resources/implementation-playbook.md, for detailed patterns and examples beyond this overview.

Backend and API engineers building fault-tolerant systems who need concrete retry, circuit-breaker, and error-messaging patterns rather than ad-hoc try/catch blocks.