How does this skill prevent cascading failures?

It guides you in implementing isolation patterns like thread-pool bulkheads, request timeouts, and circuit breakers to ensure a single failing component doesn't crash the entire system.

Does this skill help with observability?

Yes, it provides instructions for instrumenting critical paths with metrics, logs, and traces to ensure you can detect and diagnose issues before they impact the end user.

What is the difference between SLA, SLO, and SLI in this skill?

An SLA is the legal agreement with users, an SLO is your internal performance target, and an SLI is the specific metric (like error rate) used to measure if you are meeting those targets.

When should I use the Reliability Design skill?

Use it during the architecture phase of a new project, when preparing for high-scale events, or when conducting post-mortems to improve existing system stability.

Reliability Design Architect

Name: Reliability Design Architect
Author: sethdford

bysethdford

•

Cloud Infrastructure

Architects resilient software systems that minimize downtime through fault tolerance, automated recovery patterns, and SRE best practices.

The Reliability Design skill enables Claude to guide developers and architects through the creation of highly available systems using industry-standard principles from Google SRE and Nygard's Release It!. It provides a structured framework for defining measurable service levels (SLAs, SLOs, and SLIs), performing failure mode analysis, and implementing defensive architectural patterns like circuit breakers, bulkheads, and graceful degradation. This skill is essential for teams looking to reduce Mean Time To Recovery (MTTR), increase Mean Time Between Failures (MTBF), and ensure that distributed systems remain stable under stress or component failure.

Key Features

01Failure mode and effects analysis (FMEA) for components

02Automated recovery and failover mechanism planning

03Observability instrumentation for critical path monitoring

04Fault isolation using bulkheads and circuit breakers

05Service Level (SLA/SLO/SLI) definition and measurement

069 GitHub stars

Use Cases

01Improving system uptime and reducing Mean Time To Recovery (MTTR)

02Designing disaster recovery strategies for mission-critical cloud services

03Implementing graceful degradation patterns for microservices architectures

Key Features

01Failure mode and effects analysis (FMEA) for components

02Automated recovery and failover mechanism planning

03Observability instrumentation for critical path monitoring

04Fault isolation using bulkheads and circuit breakers

05Service Level (SLA/SLO/SLI) definition and measurement

069 GitHub stars

Use Cases

01Improving system uptime and reducing Mean Time To Recovery (MTTR)

02Designing disaster recovery strategies for mission-critical cloud services

03Implementing graceful degradation patterns for microservices architectures