ts-resilience

When to Use This Skill

Use when you need to:

• Decide how a failed network call should be retried, if at all
• Protect your own API routes/tRPC procedures from being overwhelmed
• Make a mutation (checkout, payment, booking) safe to retry without double-executing it
• Handle N users racing to claim the same limited resource (last seat, last item in stock)
• Stop calling a downstream dependency that's already failing, instead of hammering it

Trigger keywords: retry, exponential backoff, jitter, circuit breaker, timeout, rate limiting, idempotency key, thundering herd, bulkhead, resilience, fault tolerance, last seat, race condition checkout, overselling, distributed lock, AbortSignal.timeout, 429 too many requests, network resilience.

Freshness rule: the underlying runtime primitives shift faster than the patterns themselves — AbortSignal.timeout/AbortSignal.any and WinterCG-aligned fetch are recent additions; recheck Node's current LTS for what's native before reaching for a library to do what the platform now does natively.