Ultraperf

This is a Hermes-native ultraperf workflow skill.

Why This Exists

ultraperf exists because most performance work starts unlocalized: something is slow, leaking, or expensive and nobody knows where. It forces measurement before edits, one hypothesis at a time, executor-owned changes, and a regression budget, so an optimization loop cannot end in unverified claims.

Do Not Use When

• Metric, baseline, budget, and benchmark command are already declared for one measurable goal; use performance-goal.
• The ask is to judge code quality, structure, or correctness rather than measured cost; use code-review.
• The ask is to score model or agent output quality on a task suite; use agent-evaluation.
• The request is a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or one already-identified slow query or hotspot fix; handle it directly instead of opening a performance loop.

Examples

Good example: