From backend-engineering
Make the backend survive its dependencies: timeout every outbound call, retry idempotent-only with exponential backoff + jitter, add circuit breakers and bulkheads, define a graceful-degradation mode, and design idempotent background workers with DLQs and backpressure.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-engineering:backend-resilienceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every outbound call has one (sized to the dependency's SLO). No timeout = cascading outage.
Every outbound call has one (sized to the dependency's SLO). No timeout = cascading outage.
Idempotent only, bounded, exponential backoff + jitter (avoid synchronized storms). A retry on a non-idempotent call = a duplicate.
Circuit breaker (fail fast on a failing dep) + bulkhead (one slow dep can't starve the rest).
Define the degraded mode (stale cache / queued / clear error). Workers: idempotent + DLQ + bounded queue (backpressure, not unbounded growth).
npx claudepluginhub mcorbett51090/ravenclaude --plugin backend-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.