Reliability Design

Design systems that fail gracefully and recover automatically. Use when defining SLAs, designing for fault tolerance, or improving uptime.

48 stars 10 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill reliability-design
Manual install
git 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-design

Personal 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.
Read the full skill on GitHub

Details

Skill name
reliability-design
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

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.