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.

원본 보기