error-handling

Standardize error handling with typed error hierarchies and HTTP mappings.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/BigPapiCB/Universal-Claude-Skills --skill error-handling-bigpapicb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/BigPapiCB/Universal-Claude-Skills/tree/main/error-handling
Command: npx skills add https://github.com/BigPapiCB/Universal-Claude-Skills --skill error-handling-bigpapicb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes error handling across applications by providing a reusable error model and consistent messaging to users.

Core Features & Use Cases

  • Decision trees for error routing, distinguishing recoverable vs programming vs infrastructure failures.
  • A multi-language error type hierarchy (AppError, NotFoundError, ValidationError, AuthError, ConflictError).
  • Propagation rules across layers (Repository/DB, Service, Controller, Global handler).
  • User-facing vs internal error guidance and HTTP mapping.

Quick Start

Design and implement a shared AppError base class and a minimal set of derived errors to standardize error handling.

Frequently Asked Questions about error-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize error handling across backend services?▼

Standardize backend error handling by implementing a reusable AppError base class with a typed hierarchy, enforcing consistent behavior and safe defaults across your codebase.

What is the best way to map internal exceptions to HTTP API errors?▼

Map exceptions to HTTP API errors using propagation rules across architectural layers, routing recoverable, programming, and infrastructure failures to accurate status codes and user-facing messaging.

Does this error handling design pattern work with both Python and TypeScript?▼

Yes, the error handling design pattern supports both Python and TypeScript, enforcing a defined interface and providing examples for consistent multi-layer error propagation in both languages.

How do I propagate errors correctly across repository, service, and controller layers?▼

Propagate errors across layers by applying defined rules for repository, service, controller, and global handlers, distinguishing user-facing messaging from internal error guidance.

When should I distinguish between recoverable errors and programming failures in backend error routing?▼

Distinguish recoverable errors from programming failures using decision trees for error routing, separating infrastructure failures from application logic to determine safe defaults and user-facing messaging.