kmp-resilience

When to Use This Skill

Use when you need to:

• Decide how a failed network or native-resource call should be retried, if at all
• Protect a Ktor server route from being overwhelmed
• Make a mutation (checkout, payment, claiming a limited resource) safe to retry without double-executing it
• Classify an error as recoverable (retry, recreate the resource) vs fatal (surface to the caller, stop retrying)
• Audit whether resilience handling exists symmetrically across every platform-specific implementation of a capability, not just the one tested most

Trigger keywords: retry, exponential backoff, jitter, circuit breaker, timeout, rate limiting, idempotency key, HttpRequestRetry, transient error, fatal error, recoverable error, device lost, connection lost, resilience, backend parity, platform parity.