Why does this skill recommend avoiding base error classes?

Shared base error classes create tight coupling between different modules or contexts. Creating specific errors for each context allows them to evolve independently and contain relevant metadata.

What is the Result pattern and when should I use it?

The Result pattern returns a success or failure object instead of throwing exceptions. Use it for expected business failures, like 'User Not Found', where the caller should be forced to handle the failure case.

Does this skill work with TypeScript validation libraries?

Yes, it specifically provides patterns and examples for using Zod for boundary validation and domain-level integrity checks.

How do circuit breakers improve system reliability?

Circuit breakers prevent a system from repeatedly trying an operation that is likely to fail, such as calling a down service. This prevents cascading failures and allows the external service time to recover.

Error Handling Patterns

Name: Error Handling Patterns
Author: marcioaltoe

bymarcioaltoe

•

API Development

Implements robust, context-specific error handling and resilience patterns for backend systems and APIs.

About

This skill guides developers in implementing production-grade error handling strategies, moving beyond basic try-catch blocks to include advanced patterns like the Result pattern, circuit breakers, and retry logic. It emphasizes context-specific error types to avoid coupling in modular monoliths and Clean Architecture, ensuring that failure scenarios are handled gracefully with rich metadata and structured logging. By applying these patterns, you can build systems that provide clear feedback to callers and maintain high reliability even when external dependencies fail.

Key Features

Resilience patterns including Retry logic and Circuit Breakers
Structured logging for improved system observability
7 GitHub stars
Context-specific exception types to prevent module coupling
Result pattern implementation for explicit failure handling
Input and domain-level validation strategies using Zod

Use Cases

Designing robust API error responses and validation logic
Building resilient integrations with flaky external web services
Implementing domain-driven error handling in Clean Architecture projects

About

Key Features

Resilience patterns including Retry logic and Circuit Breakers
Structured logging for improved system observability
7 GitHub stars
Context-specific exception types to prevent module coupling
Result pattern implementation for explicit failure handling
Input and domain-level validation strategies using Zod

Use Cases

Designing robust API error responses and validation logic
Building resilient integrations with flaky external web services
Implementing domain-driven error handling in Clean Architecture projects