Perf Design

Performance and observability design, optimization, and program-level strategy for any production or runtime system — applied before a problem ships, or ahead of a measured optimization pass, so the instrumentation and budgets are right the first time. Provenance lives in skill.json; this file is runtime routing only.

Produces: a design-doc.md (instrumentation / SLO / tracing / budget design), optimize-plan.md (profile-first, before/after-gated reductions to a known-slow path), or strategy-doc.md (cross-surface program roadmap) — each a concrete good-shaped pattern with testable acceptance criteria.

Core principle

Design the measurement before you need it, and never optimize a path you have not profiled. The cheapest time to fix a perf or observability gap is before the symptom — name the SLI, the span attribute, the latency budget, or the profile-gated change concretely rather than describing principles abstractly.