global-error-handling

coreyja's avatarfrom coreyja

Implement robust error handling with user-friendly messages, specific exception types, centralized error boundaries, and graceful degradation strategies. Use this skill when implementing error handling logic in any part of the application. When writing try-catch blocks, error boundaries, or exception handlers. When validating input and failing fast with clear error messages. When handling API errors, network failures, or external service timeouts. When implementing retry strategies with exponential backoff. When ensuring resources are properly cleaned up in finally blocks. When displaying error messages to users without exposing technical details. This skill applies to all error handling across frontend and backend code.

⭐6stars🔀1forks📁View on GitHub🕐Updated Nov 19, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill enables the implementation of robust, centralized error handling frameworks across both frontend and backend systems. It focuses on enhancing software resilience through specific exception types, graceful degradation, and automated retry strategies while ensuring a secure and user-friendly experience by masking technical implementation details.

Use Cases

  • Developing centralized error boundaries in modern UI frameworks to prevent total application crashes and provide fallback interfaces.
  • Designing resilient API integration layers that handle network failures and service timeouts using exponential backoff retry logic.
  • Standardizing exception management to ensure consistent input validation and 'fail-fast' mechanisms across distributed systems.
  • Implementing secure error reporting that provides actionable feedback to end-users without exposing sensitive system architecture or stack traces.
  • Managing resource lifecycle and cleanup in complex operations to prevent memory leaks and file handle exhaustion during failure states.
nameGlobal Error Handling
descriptionImplement robust error handling with user-friendly messages, specific exception types, centralized error boundaries, and graceful degradation strategies. Use this skill when implementing error handling logic in any part of the application. When writing try-catch blocks, error boundaries, or exception handlers. When validating input and failing fast with clear error messages. When handling API errors, network failures, or external service timeouts. When implementing retry strategies with exponential backoff. When ensuring resources are properly cleaned up in finally blocks. When displaying error messages to users without exposing technical details. This skill applies to all error handling across frontend and backend code.

Global Error Handling

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global error handling.

When to use this skill

  • When implementing error handling logic in any application code
  • When writing try-catch blocks or error boundaries in components
  • When handling API errors, network failures, or timeout scenarios
  • When validating input and failing fast with explicit error messages
  • When implementing retry strategies with exponential backoff for transient failures
  • When cleaning up resources (file handles, connections, locks) in finally blocks
  • When using specific exception types rather than generic error classes
  • When designing systems with graceful degradation for non-critical service failures
  • When centralizing error handling at controller, API, or component boundaries
  • When displaying user-friendly error messages without exposing security information

Instructions

For details, refer to the information provided in this file: global error handling