What problem does it solve? Building API integrations that survive real-world failures is hard: duplicate webhook deliveries, transient 503s, cascading downstream outages, and lost jobs all break naive integrations. This Skill provides a structured protocol for designing and generating production-hardened API automation workflows where every call has a timeout, every write is idempotent, and every failure is typed and observable. ## Core Features & Use Cases - Resilience Pattern Taxonomy: Classifies workflows (single call, sequential chain, fan-out, event-driven, long-running, bidirectional sync) and maps them to patterns like idempotency keys, exponential backoff, circuit breakers, dead letter queues, sagas, and the outbox pattern. - TypeScript Implementation Generation: Produces concrete code using ky/fetch, p-retry or cockatiel for retries and circuit breaking, BullMQ for queued work, and OpenTelemetry spans for tracing. - Idempotency & Observability Enforcement: Generates deterministic idempotency-key handling with Redis and a checklist requiring spans, structured retry logs, latency metrics, and alert thresholds per workflow. - Use Case: A user asks to build a Stripe webhook processor that handles duplicate deliveries; the Skill designs the idempotency-key flow, retry policy, DLQ fallback, and emits the instrumented TypeScript implementation. ## Quick Start Ask the assistant to design a resilient integration, for example: "Build a webhook processor for Stripe that handles duplicate deliveries with retry logic and a dead letter queue."
