Perf Design

Use to DESIGN or optimize the performance and observability of a production or runtime system — design instrumentation, SLOs/error-budget policy, tracing topology, latency budgets, or metric selection up-front for a new or expanding system; plan a profile-first optimization pass on a known-slow path with before/after measurement gates; or shape a program-level observability and reliability strategy across logs, metrics, and traces. Triggers on "design our SLOs", "what spans/metrics should we emit", "plan a tail-latency optimization", "cut our log bill without losing recovery value", "observability roadmap". Emits a design doc, optimization plan, or strategy doc with concrete good-shaped patterns and acceptance criteria. Do NOT use to AUDIT or diagnose an existing system (use perf-audit), for developer-facing or local build/inner-loop performance (use dx-design), or for end-user product UX (use ui-design to build it, ux-audit to audit it).

mkdir -p ~/.claude/skills/perf-design
curl -L https://claudskills.com/skills/perf-design/SKILL.md \
  -o ~/.claude/skills/perf-design/SKILL.md

@misc{perf-design-2026,
  author    = {Thulr},
  title     = {Perf Design [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/perf-design/}
}