Solo Unicorn Club logo

CLAUDE.md Configs

DevOps/SRE Config

A CLAUDE.md for DevOps teams with incident and change management

// First 7 days

What can be running fast.

01

Get a ready-to-run system that replaces blank-page setup.

02

Ship a usable package with 8 included files and working structure.

03

Move from purchase to first setup in about 3 min.

// Included files

What is inside the package.

CLAUDE.md
conventions/severity-levels.md
conventions/change-management.md
conventions/monitoring.md
conventions/on-call.md
templates/runbook.md
templates/post-mortem.md
README.md

Description

What is DevOps/SRE Config?

CLAUDE.md for DevOps/SRE teams. Incident severity levels, change management protocols, monitoring conventions, runbook standards, and on-call procedures.

claude-code

Upgrade path

  • 01Start with this package and validate the workflow.
  • 02Add specialized skills or bundles once the core system is stable.
  • 03Use the community to sharpen positioning, demos, and feedback loops.
PreviewCLAUDE.md
# CLAUDE.md — DevOps/SRE Config

## Incident Severity Levels
- **SEV1**: Complete outage, all users affected → page immediately
- **SEV2**: Partial outage, >10% users → page during business hours
- **SEV3**: Degraded, workaround exists → next business day
- **SEV4**: Cosmetic / minor → backlog

## Change Management
- All production changes require a change request
- Deploy windows: Tue-Thu, 10am-2pm (avoid Fridays)
- Rollback plan required before every deploy
- Feature flags for all new user-facing features

## Monitoring Conventions
- Every service must expose /health and /metrics
- Alert on symptoms (error rate), not causes (CPU)
- SLO: 99.9% availability, p99 latency < 500ms
- PagerDuty escalation: 5 min ack, 15 min response

// Community acceleration

Use the room after the purchase.

Bring your workflow into the Solo Unicorn community for sharper feedback, operator critique, and more visibility once the system is live.

Discuss implementation