resiliencia

Implement error boundaries, retries, and circuit breakers for resilient applications.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Hashzin-0/Curion --skill resiliencia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resiliencia
Source: https://github.com/Hashzin-0/Curion/tree/main/.opencode/skills/resiliencia
Command: npx skills add https://github.com/Hashzin-0/Curion --skill resiliencia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents application crashes and poor user experiences caused by runtime errors, network failures, and unexpected or malformed data by providing patterns and components for graceful degradation and recovery.

Core Features & Use Cases

  • Error boundaries & UI fallbacks: Isolate component errors and display recoverable fallback UIs without crashing the whole app.
  • Data fallback & loading states: Use cache-first strategies, skeleton loaders, and stale-data warnings to keep interfaces responsive when network calls fail.
  • Reliability controls: Implement retry with exponential backoff and circuit breakers for external services to improve availability and avoid cascading failures.
  • Use case: Wrap a dashboard and critical user profile flows with ErrorBoundary, use a cached useUserData hook for offline fallback, and protect third-party API calls with retry and a circuit breaker.

Quick Start

Wrap critical pages and data fetches with an ErrorBoundary, implement a cache-first useUserData hook with skeletons, and add retry with exponential backoff plus a circuit breaker for external API calls.

Frequently Asked Questions about resiliencia

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle runtime errors and external API failures without crashing my application?

Handle runtime errors and external API failures by wrapping critical pages in error boundaries, using cache-first hooks with skeleton loaders, and adding retry with exponential backoff plus circuit breakers to isolate faults and display fallback UIs.

What is the best way to implement a circuit breaker for third-party API calls?

The best way to implement a circuit breaker for third-party API calls is to wrap external service integrations with reliability controls that monitor failures and trip the circuit to block requests, preventing cascading failures and allowing recovery time.

How do I add retry with exponential backoff to network requests?

Add retry with exponential backoff to network requests by applying reliability controls to external service calls, which automatically retry failed operations with progressively increasing delays to improve availability without overwhelming the target service.

Can I use cache fallback strategies to keep UI responsive when data fetching fails?

Yes, you can use cache-first strategies, skeleton loaders, and stale-data warnings as fallback mechanisms to keep interfaces responsive and display recoverable UIs when background data fetching or network calls fail.

Does this approach work for both frontend components and background data fetching?

Yes, this approach works for both frontend components and background data fetching by isolating component errors with error boundaries and protecting external API integrations with retry and circuit breaker patterns across user-facing pages.