One install gives your agent a measured pre-launch performance fix: a production-mode baseline, four read-only subagents auditing twenty known slow-downs across images, bundles, database queries and servers, then one fix pass — proved with the same mobile Lighthouse run, three times, before and after.
install
Detects Claude Code, Cursor, Codex, Qoder and more, then writes the skill into the right folder. Add -l to see what the repo ships before anything is installed.
npx skills add arm-pz/pre-ship-performance-audit
the four groups
The subagents inspect and report — file, route, evidence, proposed fix. The main agent implements centrally, after the findings are prioritized into a P0–P3 backlog.
The bytes most pages actually drown in.
Ship less code, render it earlier.
The one group that must read query plans, not folklore.
Where the request actually travels.
Before any fix: production build or approved preview, mobile Lighthouse ×3 on the homepage and the slowest pages, medians recorded with exact commands. After: the same URLs, the same configuration, the same device. No comparable conditions, no percentage claim.
house rules
The audit fixes slowness by removing waste, never functionality. If a speedup could only come from dropping a feature or a dependency, that is a question for you, with expected benefit and trade-offs written out first.
If a production build or preview cannot run, the skill says so instead of inventing numbers. Substitutes are labeled. And "this is a best practice" never counts as evidence of your bottleneck — the file, the route and the measurement do.
Removing dependencies, changing deployment regions, or touching database schema, indexes, RLS or settings stops for your go-ahead. And a user-specific response is never pushed into a shared cache — speed without data leaks.
Free, open, and it runs entirely inside the agent you already use.
Install pre-ship-performance-audit Read the source