🛡️ Core Philosophy: Assume everything will fail, and design systems that degrade gracefully.
When to use
Use this skill when implementing network requests (fetching data, posting mutations), designing backend integrations, writing microservices communication, creating resilience decorators, or defining request timeout and queue limits.
When not to use
Do not use this skill for styling layout states, analytics event naming schemas, or setting up auth sessions.
Trigger cues
- Key terms: circuit breaker, exponential backoff, jitter, timeout, fallback state, bulkhead, resilience, retry policy, microservice fault, network retry.
- Designing fetch decorators, handling API timeouts, writing retry functions, or isolating service calls.
Routing boundary
- Primary for network fault management, retry systems, circuit-breaker patterns, timeout policies, and API client wrappers.
- Secondary to
system-architecture-rules for high-level structure.
Inputs required
- Target programming language and network library (e.g., Axios, fetch in TS, URLSession in Swift)
- Specific latency requirements and timeout limits
- Source of truth:
references/source.md
Instructions
- Detect Stack: Inspect the workspace files to identify the project's existing programming language and network libraries (e.g., TypeScript/Fetch/Axios, Swift/URLSession, Python/requests).
- Do Not Migrate: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.
- Read references/source.md to understand timeouts, retries, jitters, and circuit breakers.
- Set explicit request timeouts on all network clients to prevent resources from locking up.
- Bound retries by attempts or elapsed time. Retry only operations that are safe or protected by idempotency, using exponential backoff with random jitter.
- Design circuit-breaker wrappers (Closed, Open, Half-Open states) around downstream services.
- Outline clear fallback behaviors (serving stale cache, cached user configurations, or empty lists).
Completion gate
Before reporting completion, verify the applicable binary contracts in evals/cases.json: explicit timeout, bounded safe retries with backoff and jitter, all three circuit states with a recovery probe, and a visible bounded fallback.
Output format
- Primary decision/output: Resiliency logic wrapping network requests, retry helper implementations, and circuit-breaker config.
- Summary: One-paragraph overview of request resiliency and fault strategy.
- Actions: Verification checklist for timeout limits, jitter distribution, and circuit-breaker threshold safety.
1---2name: resiliency-circuit-breakers3description: Trigger: circuit breaker, exponential backoff, jitter delay, connection timeout, API retry. Scope: Client request resiliency, API retries, fault isolation. Boundary: Excludes visual state loading skeletons.4---56# 🛡️ Core Philosophy: Assume everything will fail, and design systems that degrade gracefully.78## When to use910Use this skill when implementing network requests (fetching data, posting mutations), designing backend integrations, writing microservices communication, creating resilience decorators, or defining request timeout and queue limits.1112## When not to use1314Do not use this skill for styling layout states, analytics event naming schemas, or setting up auth sessions.1516## Trigger cues1718- Key terms: circuit breaker, exponential backoff, jitter, timeout, fallback state, bulkhead, resilience, retry policy, microservice fault, network retry.19- Designing fetch decorators, handling API timeouts, writing retry functions, or isolating service calls.2021## Routing boundary2223- Primary for network fault management, retry systems, circuit-breaker patterns, timeout policies, and API client wrappers.24- Secondary to `system-architecture-rules` for high-level structure.2526## Inputs required2728- Target programming language and network library (e.g., Axios, fetch in TS, URLSession in Swift)29- Specific latency requirements and timeout limits30- Source of truth: `references/source.md`3132## Instructions33341. **Detect Stack**: Inspect the workspace files to identify the project's existing programming language and network libraries (e.g., TypeScript/Fetch/Axios, Swift/URLSession, Python/requests).352. **Do Not Migrate**: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.363. Read [references/source.md](references/source.md) to understand timeouts, retries, jitters, and circuit breakers.374. Set explicit request timeouts on all network clients to prevent resources from locking up.385. Bound retries by attempts or elapsed time. Retry only operations that are safe or protected by idempotency, using exponential backoff with random jitter.396. Design circuit-breaker wrappers (Closed, Open, Half-Open states) around downstream services.407. Outline clear fallback behaviors (serving stale cache, cached user configurations, or empty lists).4142## Completion gate4344Before reporting completion, verify the applicable binary contracts in `evals/cases.json`: explicit timeout, bounded safe retries with backoff and jitter, all three circuit states with a recovery probe, and a visible bounded fallback.4546## Output format4748- Primary decision/output: Resiliency logic wrapping network requests, retry helper implementations, and circuit-breaker config.49- Summary: One-paragraph overview of request resiliency and fault strategy.50- Actions: Verification checklist for timeout limits, jitter distribution, and circuit-breaker threshold safety.
coreyone