Use when implementing chaos engineering, designing fault injection experiments, or building resilience testing practices. Covers chaos principles and experiment design.
View on GitHubmelodic-software/claude-code-plugins
systems-design
plugins/systems-design/skills/chaos-engineering-fundamentals/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/melodic-software/claude-code-plugins/blob/main/plugins/systems-design/skills/chaos-engineering-fundamentals/SKILL.md -a claude-code --skill chaos-engineering-fundamentalsInstallation paths:
.claude/skills/chaos-engineering-fundamentals/# Chaos Engineering Fundamentals Principles and practices for chaos engineering - proactively discovering system weaknesses through controlled experiments. ## When to Use This Skill - Implementing chaos engineering practices - Designing fault injection experiments - Building confidence in system resilience - Discovering hidden failure modes - Validating disaster recovery ## What is Chaos Engineering? ```text Chaos Engineering = Proactive resilience testing Traditional testing: "Does it work when everything is right?" Chaos engineering: "Does it work when things go wrong?" Principle: Build confidence in the system's ability to withstand turbulent conditions in production. Not about breaking things randomly. About controlled experiments to learn. ``` ## The Chaos Engineering Loop ```text ┌─────────────────────────────────────────────────────────┐ │ CHAOS ENGINEERING LOOP │ │ │ │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ │ │ Define │────►│ Inject │────►│ Observe │ │ │ │ Steady │ │ Chaos │ │ Results │ │ │ │ State │ │ │ │ │ │ │ └─────────┘ └─────────┘ └────┬────┘ │ │ ▲ │ │ │ │ │ │ │ │ ┌─────────┐ │ │ │ └──────────│ Improve │◄─────────┘ │ │ │ System │ │ │ └─────────┘ │ └─────────────────────────────────────────────────────────┘ ``` ## Core Principles ### 1. Build Hypothesis Around Steady State ```text Steady State = Normal system behavior Define measurable indicators: - Request success rate: 99.9% - Latency p99: < 200ms - Orders processed/minute: > 100 - User sessions active: > 10,000 Hypothesis format: "When [fau