Purpose and inputs
Find performance issues with a measured baseline. Quality budgets live in /f-quality. Do not invent SLOs or impact percentages. Report-only unless the user asked to implement.
Steps
- Read Quality overlay budgets if present. Capture a baseline with the repo profiler, traces, tests, or
ghjob timing — not estimates. - Locate the owning hot path (query, render, allocation) with that evidence.
- Recommend the smallest change. Implement only when authorized. Re-measure after a change.
- If a new budget is required, defer to
/f-quality.
Verification
- Recommendations cite a baseline measurement or an explicit "not measured" label.
- No fabricated timings or percentages.
- No unsolicited commit.
Handoff
Report baseline, suspected cause, and proposed change. Say when measurement is still missing.