← ClaudeAtlas

inp-auditlisted

Statically audits a React or Next.js codebase for code patterns that commonly cause poor INP (Interaction to Next Paint), ranks them by likely impact and shows a concrete before/after fix built from the user's own code. Use this skill whenever the user mentions INP, Interaction to Next Paint, Core Web Vitals, long tasks, a blocked main thread, slow input, typing lag, a button that "feels laggy", a UI that freezes on click, a page that hangs when filtering or searching, or asks to audit React/Next.js performance or responsiveness, even if they never say "INP". Also use it when the user opens a React/Next.js project and complains that interactions feel sluggish, or wants a CI check for INP regressions. Not for load-time metrics alone (LCP/CLS/bundle size) or non-React projects.
radyelkasas/inp-audit · ★ 0 · Web & Frontend · score 72
Install: claude install-skill radyelkasas/inp-audit
# inp-audit Find the code that most likely makes interactions slow, explain it in plain words, and give one safe fix per finding. The audit is **static analysis of likely risks, not a measurement**: it reads code shape, not runtime behaviour. Every answer you give from it has to say so and end with how to verify. ## Workflow 1. **Locate the app.** Use the folder with the `package.json` that depends on `react` or `next`. In a monorepo, run once per app (`apps/web`, …). 2. **Run the engine** (read-only on source files; it writes only the report): ```bash node <skill-dir>/scripts/audit.js <app-dir> --json ``` - stdout is JSON (use it to reason); `<app-dir>/inp-audit-report.md` is saved for the user. Creating that one report file is expected (it's the deliverable); tell the user where it is. Use `--no-save` if they don't want a file in the repo, or `--out <path>` to put it elsewhere. - Exit codes: `0` nothing at/above `--fail-on`, `1` High findings exist, `2` not a React project or usage error. - If it prints that the project isn't React/Next.js, **stop** and tell the user. Don't improvise a manual audit of a Vue/Svelte/Angular app with these rules. - If it says no parser is available, run `npm install` inside `<skill-dir>/scripts` (installs `@babel/parser`); a vendored copy normally makes this unnecessary. 3. **Check the findings by hand before presenting them.** Open every High finding and anything else that could reach the top 3 at `file:line`. The engi