Reliability Design
Design systems that fail gracefully and recover automatically. Use when defining SLAs, designing for fault tolerance, or improving uptime.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill reliability-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/quality-attributes/skills/reliability-design ~/.claude/skills/reliability-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Reliability Design Build systems that anticipate failures, degrade gracefully, and recover automatically. Design for MTBF and MTTR trade-offs. ## Context You are designing for reliability. The user faces uptime requirements, wants to reduce MTTR, or needs to design disaster recovery. Read their current SLAs and failure modes. ## Domain Context Based on Nygard's Release It! and Google's SRE practices: - **MTBF (Mean Time Between Failures)**: How long before next failure? Increase by building fault-tolerant systems - **MTTR (Mean Time To Recovery)**: How long to recover? Decrease by automating recovery and alerting - **Graceful Degradation**: When components fail, reduce functionality rather than crashing entirely - **Fault Isolation**: Failures contained to one component; don't cascade - **Observability**: Can you see problems before users do? Metrics, logs, traces for every critical path ## Instructions 1. **Define SLA/SLO/SLI**: - **SLA**: Service level agreement (e.g., 99.99% uptime) with penalties - **SLO**: Service level objective (internal target, e.g., 99.95%) - **SLI**: Service level indicator (measured metric, e.g., "request success rate") 2. **Map Failure Modes**: For each critical component, ask: "What happens if this fails?" Example: database down → query service fails → frontend shows error.
Details
- Skill name
reliability-design- Repository
- sethdford/claude-skills
- Path
architect/quality-attributes/skills/reliability-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Reliability Design skill do?
Design systems that fail gracefully and recover automatically. Use when defining SLAs, designing for fault tolerance, or improving uptime.
How do I install the Reliability Design skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Reliability Design popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
State Machine
48sethdford/claude-skills
Model complex UI behavior as finite state machines with states, events, and transitions.
Reactive Patterns
48sethdford/claude-skills
Streams, observables, event-driven reactive systems, backpressure, and reactive programming.
Summarize Interview
48sethdford/claude-skills
Summarize a user interview transcript into structured insights with key themes, quotes, and action items. Use after conducting user interviews to extract and share findings efficiently.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.