Performance Profiling

Use this skill to run the repo’s performance checks (or propose a minimal plan if they don’t exist), compare results to budgets/baselines, and produce an actionable regression summary.

This skill is intentionally strict about “evidence”:

• If you did not measure it, label it as a risk hypothesis.
• If you did measure it, include the exact command and the key output.

Workflow

1. Discover perf tooling, baselines, and budgets.

• Inspect package.json scripts for: perf, benchmark, profile, lighthouse, bundle, analyze, size, stats.
• Look for tooling/config files:
  • next.config.* (bundle/analyze hooks, headers, compression toggles)
  • lighthouserc.*, lighthouse.*
  • size-limit.*, .size-limit.*, bundlesize.*
  • webpack.config.* / analyzer config (if present)
• Check docs under docs/ (or repo root docs) for perf budgets and release gates.