error-handler

Custom error classes standardize exception handling across your codebase. Create typed error subclasses like ValidationError, NotFoundError, and DatabaseError that extend a base AppError class, allowing you to catch and handle specific error types with structured context and meaningful messages.

Use consistent error response formats with structured logging and safe propagation. Define custom error classes for domain-specific failures, wrap unknown exceptions, log context-rich messages, and return predictable client-facing payloads so frontend and backend communicate failures reliably.

Structured logging captures error context at each layer while propagation strategies determine when to retry, fail gracefully, or clean up resources. Combine typed errors, context enrichment, and logging patterns to trace failures through API calls and service integrations without losing diagnostic information.

Yes. This Skill provides battle-tested patterns and custom error class structures applicable to both TypeScript and Python, letting you maintain consistent exception management practices across mixed-language backends, web services, and frontend-backend integrations.

Retry logic and resource cleanup are critical for resilient services. The Skill covers strategies for retrying transient failures, ensuring proper cleanup on error paths, and implementing graceful degradation so your application remains stable when failures occur.

Validation errors catch bad user input early with actionable messages, while database errors indicate infrastructure or query failures requiring different recovery paths. Separating them into distinct custom error classes enables precise handling, logging, and client feedback for each failure type.