Overview

Implement comprehensive error handling to make code robust and resilient to failures while preserving a good user experience. It covers error detection, strategy, recovery mechanisms, and UX considerations to gracefully handle failures across APIs, services, and UI.

How This Skill Works

Begin by detecting failure points and unhandled conditions, including missing validations and async operations. Then apply an error handling strategy with input validation, try-catch blocks, meaningful logging, and graceful degradation. Finally add recovery mechanisms such as retries, fallbacks, circuit breakers, and proper error propagation to callers and the user.

When to Use It

• When building apps that call external services or perform IO operations and need robust failure handling
• When you must present clear error messages and appropriate status codes to users or clients
• When integrating multiple components in microservices or distributed systems
• When the UI requires loading states and error boundaries to manage failures gracefully
• When designing resilient batch jobs or data pipelines that may experience transient faults

Quick Start

1. Step 1: Identify failure points, edge cases, and unhandled conditions in your codebase
2. Step 2: Add validation, try-catch blocks, and structured logging; establish a clear error handling strategy
3. Step 3: Implement recovery mechanisms like retries, fallbacks, circuit breakers, and user facing error messages and status handling

Best Practices

• Identify potential failure points and edge cases across the codebase
• Use try-catch blocks where appropriate to catch and handle errors
• Add input validation and sanitization to prevent invalid data from causing failures
• Create meaningful error messages and logging that aid diagnosis
• Implement retry logic, fallbacks, and circuit breakers for resilient recovery

Example Use Cases

• API integration with external services using retries and graceful fallbacks
• Front end apps showing loading states, error boundaries, and user friendly messages
• Microservices with circuit breakers and proper error propagation
• Batch data pipelines with retry on transient failures
• CLI tools that surface clear actionable error information and guidance

Frequently Asked Questions