version: "1.0.0"

performance-tuning

Use this skill when speed, memory, bundle size or cost matters.

Procedure

1. Measure before changing.
2. Identify the bottleneck.
3. Make one optimization at a time.
4. Re-measure after changes.
5. Avoid trading correctness for speed.

Output

• Baseline
• Change
• After measurement
• Tradeoffs

Evidence

A good use of this skill should leave at least one concrete artifact:

• a decision, checklist, command, test result, design note, finding or patch;
• the assumptions that mattered;
• the remaining risk or verification gap.

Failure Modes

Avoid these common failures:

• giving generic advice without applying it to the task;
• skipping verification when a check is available;
• hiding uncertainty or inventing evidence;
• expanding scope beyond the user request.