error-boundaries

What problem does it solve?

This Skill helps teams decide where to catch errors to prevent cascading failures and to improve debuggability and resilience.

Core Features & Use Cases

• Boundary-first error handling: Identify where errors should be caught to minimize propagation and ensure clear failure modes.
• Architectural guidance: Provides rules for HTTP controllers, internal services, and UI boundaries to keep business logic clean.
• Gracious degradation: Enables safe fallbacks and meaningful error responses when boundaries are hit.

Quick Start

Audit your codebase to locate where errors travel across layers, remove scattered try/catch blocks, and centralize handling at the designated boundaries. Then run targeted tests to verify proper propagation and graceful degradation.