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 |

エラーをどこでキャッチするかを決定するときに使用します。エラーが伝播しすぎる場合、または伝播が不十分な場合に使用します。コンポーネント/サービスの分離を設計するときに使用します。 ソース: yanko-belov/code-craft。

原文を見る