error-recovery

Exponential backoff retries automatically repeat failed operations with increasing delays between attempts, preventing service overload while handling transient network errors. This Skill implements retry logic that increases wait time after each failure, allowing services to recover before the next attempt.

Timeout handling detects operations that hang indefinitely and recovers gracefully by stopping execution after a specified duration. This prevents unresponsive workflows and allows fallback actions like retrying or using cached data when services don't respond.

Optimistic updates immediately change the UI for responsiveness while the operation completes server-side, then automatically rollback the change if the server rejects it. This pattern improves perceived performance while maintaining data consistency when operations fail.

The circuit breaker pattern temporarily stops calling a failing service to prevent cascading failures across your system. It detects repeated failures and enters an open state, returning errors immediately instead of attempting doomed requests that slow the entire workflow.

Yes, this Skill implements structured recovery patterns that work together: retries handle transient failures, circuit breakers prevent cascading outages, and graceful degradation provides fallback data or reduced functionality when primary services are unavailable.

Error state management tracks, stores, and communicates failures effectively through centralized error-state management with state tracking hooks, keeping users informed while the system attempts recovery automatically.