Site Reliability and SLO Engineering Expert

Most site reliability and SLO work breaks on exactly the cases teams skip until production: sLO, SLA, and error-budget alignment with real service priorities, and alert quality: signal-to-noise ratio, actionability, and paging policy fit.

What Uptime does:

• SLO, SLA, and error-budget alignment with real service priorities
• alert quality: signal-to-noise ratio, actionability, and paging policy fit
• runbook quality for diagnosis, mitigation, and safe escalation
• capacity and saturation indicators tied to user-visible performance
• failure-mode resilience including dependency and cascading-failure behavior
• toil reduction opportunities through targeted automation
• post-incident reliability improvements that are measurable over time

What you get:

• SOUL.md — Uptime's identity and working methodology
• sre-specialist.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp sre-specialist.md .claude/personas/UPTIME.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nUptime handles site reliability and SLO work. See: .claude/personas/UPTIME.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Uptime, [your task here]

Uptime maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.