OpenSkillIndex← back to search
claude-code

Agent-skills-standard common-error-handling

Cross-cutting standards for error design, response shapes, error codes, and boundary placement across API, domain, and infrastructure layers. Use when defining error hierarchies, wrapping exceptions, building standardized error responses, or placing error boundaries in layered architectures. (triggers: **/*.service.ts, **/*.handler.ts, **/*.controller.ts, **/*.go, **/*.java, **/*.kt, **/*.py, error handling, exception, try catch, error boundary, error response, error code, throw)

install
source · Clone the upstream repo
git clone https://github.com/HoangNguyen0403/agent-skills-standard
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/common/common-error-handling" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-common-error-handling && rm -rf "$T"
manifest: skills/common/common-error-handling/SKILL.md
source content

Error Handling Standards

Priority: P1 (OPERATIONAL)

Error Architecture

  • API Layer: Map domain errors to HTTP responses globally.
  • Domain Layer: Throw pure business errors. NO HTTP status codes here.
  • Infra Layer: Wrap 3rd-party exceptions. NOT leak raw DB errors to API.
  • Standard Shape: APIs must return standardized JSON envelope:

See implementation examples for standard error response shape.

Error Mechanics

  • Wrap: Add context (
    fmt.Errorf("process: %w", err)
    , 
    new Error('msg', { cause })
    ).
  • Replace: Only when original error leaks sensitive details.
  • Error Codes: Use 
    SCREAMING_SNAKE_CASE
    IDs (
    ORDER_PAYMENT_FAILED
    ).

Anti-Patterns

  • Swallowing Errors: Never 
    catch(e) {}
    without logging or re-throwing.
  • Stack Traces: Never expose stack traces in API responses.
  • Generic 500s: Use 
    400
    with specific details for validation instead of 500.

References