mirrord-chaos

1# Mirrord Chaos Testing Skill
2 
3## Purpose
4 
5Help users inject artificial failures and disruptions into a mirrord session's **outgoing traffic**, to test how their app behaves under unexpected conditions. A **chaos rule** pairs a **selector** (which traffic to match) with an **effect** (what to do to it). Rules are created and managed with the **`mirrord chaos` CLI command**, and each rule is attached to a single mirrord session: it never affects other sessions or the cluster.
6 
7This skill covers two modes:
8 
91. **Interactive mode**: a developer starts a session with `mirrord exec` and manages rules with `mirrord chaos`.
102. **CI mode**: a pipeline applies rule files checked into the repo with `mirrord chaos add`, and runs tests under chaos.
11 
12## When to Use This Skill
13 
14Trigger on questions like:
15- "Add latency to my service's database connections with mirrord"
16- "How do I chaos test with mirrord?"
17- "Simulate connection failures / timeouts to an upstream service"
18- "Create / modify / delete a mirrord chaos rule"
19- "Run my integration tests with injected latency in CI"
20- "How do I use `mirrord chaos`?"
21 
22## Security (must follow)
23 
24- **Blast radius is the session, not the cluster.** Chaos rules apply only to the outgoing traffic of the process being run with mirrord. They do not touch the target workload or other cluster traffic. Still, run chaos against staging targets: a session pointed at production dependencies will experience real failures against real systems.
25…