typed-failure-handling

Designs how backend code fails on purpose: context-owned error types, the Result pattern for expected business failures, boundary and domain validation, bounded retries, circuit breakers, fallbacks, structured error logs, and safe HTTP error mapping. Use when the user asks to "handle errors properly", "implement the Result pattern", "create custom exceptions", "validate input", "add retry logic", or "add a circuit breaker". Not for frontend error boundaries, test frameworks, or hiding permanent failures behind retries.

Version

v1.0.1

Size

13 KB

Updated

2026-10-06

Your client verifies the signature before reading. This explicit manual read is available on every plan. Free automatically loads five chosen skills; paid plans automatically load relevant skills across the library.