[ PACK LIBRARY / SOFTWARE DEVELOPMENT ]
REQUIRES
Use this to measure site performance and prioritize fixes. Torque combines the local audits with Lighthouse results to report blocking scripts, oversized bundles, image problems, and render-blocking CSS.
claude plugin install web-dev@b-open-io (skills: web-dev:perf-audit, web-dev:frontend-performance; roster: Torque (web-dev:optimizer))bun run build or equivalent)bun dev or a served production build) and Chrome available for headless runs{{PROJECT_PATH}} # absolute path to the repo to audit
{{BUILD_COMMAND}} # e.g. bun run build ; the perf scripts need build output to exist
{{LOCAL_URL}} # URL the app serves on locally, e.g. http://localhost:3000
{{TARGET_ROUTES}} # 1-3 routes that matter most (home, dashboard, checkout)
You are running a full, single-session performance audit on {{PROJECT_PATH}}. You produce a scored, prioritized fix list. You do NOT change product behavior or design in this pass.
Setup:
1. Load the web-dev:perf-audit skill and follow it. Confirm a production build exists; if not, run {{BUILD_COMMAND}} first, because the bundle audit needs build output.
Do:
2. Run the full audit script from the perf-audit skill against {{PROJECT_PATH}} to get the baseline health score (0-100) plus the image, bundle, and dependency sub-reports.
3. For {{TARGET_ROUTES}} served at {{LOCAL_URL}}, load the web-dev:frontend-performance skill and run its Lighthouse pass. Capture score, LCP, TBT, and CLS per route, plus the bootup-time and main-thread breakdown for the slowest route.
4. Merge the two data sources into one ranked list. Rank by estimated user impact, not by how easy each fix is. For every item record: the metric it hurts, the evidence (file, size, or audit value), and the concrete fix.
Verify:
5. Re-read your list and drop anything you cannot back with a number from the audit output. Every line must cite a real measurement.
Negative prompts:
- Do NOT apply fixes in this run. This is a read-and-report pass; a separate playbook ships the changes.
- Do NOT change the design, framework, or dependencies.
- Do NOT invent metrics. If a script could not run (no build, Chrome missing), say so and mark that section incomplete rather than guessing.
Deliverable:
6. Return the baseline health score, per-route Lighthouse metrics, and the ranked fix list with evidence and same-day-actionable next steps.A single report: the baseline health score, per-route Lighthouse numbers (LCP/TBT/CLS), and a ranked, evidence-backed fix list you can act on the same day — no code changed yet.
sd-image-bundle-opt — Cut page weight with an image and bundle optimization pass (execute the top fixes)sd-ship-safely-chain — Ship-a-feature-safely chain: build to perf audit to test to deploysd-e2e-ci-gate — Add an e2e suite and a merge-blocking coverage gate (lock the wins in)