defensive-patterns

What problem does it solve?

Defensive-pattern selection prevents production outages and runaway costs by ensuring critical endpoints and integrations handle failures predictably instead of cascading into broader incidents.

Core Features & Use Cases

• Pattern Menu with Risk-Based Guidance: Presents production defensive categories like rate limiting, circuit breakers, timeouts, fallback responses, retries with backoff, bulkheads, centralized config, health checks, and graceful degradation, then guides prioritization by impact.
• Context-Aware Application: Reads the target module/service code when a name is provided, identifies which patterns already exist, and recommends only relevant missing ones.
• Production-Ready Implementation Prompts: Provides concrete “when to use” triggers and operational expectations (e.g., 429 for rate limiting, open/half-open states for circuit breakers, explicit timeouts for all external calls).

Quick Start

Run defensive pattern selection for the module you want to protect by calling /anti-vibe-coding:defensive-patterns with the service or module name as the argument.