performance-tool-client: Instructions file for Claude Code

Repository guide for AI agents

AGENTS.md symlinks here. Edit this file.

Single-page Next.js app showing RPC provider performance. One route /, rendered force-dynamic, with ?protocol= and ?range= (24h or 7d). Data comes from the Grafana that compare-dashboard-functions feeds; this app only reads.

Checks

npm run lint and npm run build. There is no test suite, so these are the only automated checks — run both before calling work done. For interactive changes, also load the page and click through it; the build passes on plenty that is broken at runtime.

Needs GRAFANA_API_TOKEN in .env.local or every metric reads as unavailable — a local run without it exercises the render path, not the data path, so clicking through proves less than it appears to.

Deeper sweeps are a one-off, not a per-PR gate, and deliberately not devDependencies — they add ~157 packages to a 433-package tree for something run a few times a year, against a repo that keeps its production audit at zero on purpose. Reach for them with npx when doing dead-code or dependency work:

• npx knip — unused files, exports and dependencies. The one that finds what grep misses, because it tells a function apart from a same-named property.
• npx tsc --noEmit --noUnusedLocals --noUnusedParameters — unused locals and parameters, which the committed tsconfig.json does not enable.
• npx eslint . --max-warnings 0 — fails on warnings that npm run lint prints but tolerates.
• npx madge --circular --extensions ts,tsx --ts-config tsconfig.json src/ — import cycles. --ts-config is required: without it the @/ alias goes unresolved and every aliased module is falsely reported as an orphan.
• npx depcheck — reports tailwindcss, @tailwindcss/postcss and the @types/* packages as unused. It cannot see CSS @import, a .mjs config, or ambient types, so treat those as noise; knip is right where the two disagree.