Identify error boundaries across HTTP controllers, services, and UI layers.
npx skills add https://github.com/yanko-belov/code-craft --skill error-boundaries
Please help me install this Agent Skill. Skill: error-boundaries Source: https://github.com/yanko-belov/code-craft/tree/main/skills/error-boundaries Command: npx skills add https://github.com/yanko-belov/code-craft --skill error-boundaries
This Skill helps teams decide where to catch errors to prevent cascading failures and to improve debuggability and resilience.
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.
High-intent search queries and answers about installing and using this skill.
Boundary-based error handling centralizes exception management at architectural boundaries like HTTP controllers and UI layers to prevent cascading failures and ensure clear failure modes. This approach stops errors from propagating uncontrollably across internal services.
To stop scattered try/catch blocks from polluting internal services, audit your codebase to locate where errors travel across layers, remove the scattered handlers, and centralize handling at designated architectural boundaries.
For graceful degradation, error handling should be placed at HTTP controllers, internal services, and UI boundaries. Centralizing handling at these designated boundaries enables safe fallbacks and meaningful error responses.
The best way to translate errors appropriately across architectural boundaries is to document each boundary, centralize exception handling at the boundary layer, and translate the errors into meaningful responses for the receiving layer.
Yes, you can apply boundary-first exception management to existing codebases by auditing where errors travel across layers, removing scattered try/catch blocks, centralizing handling at boundaries, and running targeted tests to verify propagation.
zeshoneStandardize ASP.NET Core 8 API responses with ResponseDTO<T> and ProblemDetails.
maxjuniorbrStandardize error handling, propagation, and graceful degradation in multi-service architectures.
gerald-icaDefine and enforce architecture and file-placement rules for Electron-style multi-process projects.
FlorianRiquelmeImplement global error handling with retry logic and user-friendly messages.
