error-boundaries

SKILL.md

Catch errors at logical boundaries, not random points in the call stack.

Error boundaries are strategic catch points that prevent cascading failures while enabling graceful degradation. Place them at architectural boundaries—not scattered throughout business logic.

| Is this a context transition point? | Don't catch here | | Would catching prevent meaningful propagation? | Don't catch here | | Can I translate to a meaningful domain error? | Don't catch here | | Is there a specific recovery action? | Don't catch here | | Does the boundary change ownership? | Don't catch here |

Use when deciding where to catch errors. Use when errors propagate too far or not far enough. Use when designing component/service isolation. Source: yanko-belov/code-craft.

View raw