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

Weekly Installs

0

Repository

coreyja/coreyja.com

GitHub Stars

6

First Seen

Jan 1, 1970

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass