chaos-engineering

When this skill is activated, always start your first response with the 🧢 emoji. # Chaos Engineering A practitioner's framework for running controlled failure experiments in production systems. This skill covers how to design, execute, and learn from chaos experiments - from simple latency injections to full game days - with an emphasis on safety, minimal blast radius, and translating findings into durable resilience improvements. --- ## When to use this skill Trigger this skill when the user: - Wants to design a chaos experiment or fault injection scenario - Is setting up a chaos engineering program from scratch - Needs to implement network latency, packet loss, or service dependency failures - Is planning or facilitating a game day exercise - Needs to validate circuit breakers, retries, or failover logic under real failure conditions - Wants to measure and improve MTTR (Mean Time to Recovery) - Is evaluating chaos tooling (Chaos Monkey, Litmus, Gremlin, AWS Fault Injection Simulator) Do NOT trigger this skill for: - Writing standard retry or circuit breaker code without the intent to test it under chaos (use backend-engineering skill) - Load testing or performance benchmarking that does not involve failure injection (use performance-engineering skill) --- ## Key principles 1. **Define steady state before breaking anything** - You cannot detect a deviation without a baseline. Before every experiment, define the precise metric (p99 latency, error rate, success...