nextjs-review
Skill2 starsChanged 8 months agoMITView on GitHub
Next.js App Router audit: Core Web Vitals (LCP/CLS/FID), Server vs Client Components, caching strategy, bundle size, image optimization, SEO metadata. Sources: Google web.dev, Next.js Production Checklist.
In this repository34 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- accessibility-reviewSkill
- api-designSkill
- audit-runnerSkill
- auto-fixSkill
- brainstormSkill
- compliance-checkSkill
- continuous-testing-guardianSkill
- contract-lookupSkill
- explainSkill
- idea-validatorSkill
- load-test-auditSkill
- monthly-reviewSkill
- new-featureSkill
- perfection-auditSkill
- performance-deep-auditSkill
- post-code-security-auditSkill
- pre-code-security-checkSkill
- pre-deploymentSkill
- project-setupSkill
- pro-samuelSkill
- quick-auditSkill
- risk-scoreSkill
- roadmap-builderSkill
- secret-scannerSkill
- seo-auditSkill
- supabase-reviewSkill
- token-economySkill
- typescript-reviewSkill
- ux-cognitive-load-checkSkill
- ux-heuristic-auditSkill
- ux-progressive-disclosureSkill
- welcomeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before a production release
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/nextjs-review: Next.js App Router Audit
When to use
- Before a production release
- Performance audit (LCP > 2.5s, CLS > 0.1)
- Review of a new page or feature
- Bundle size optimization
Criteria (Google HEART + Core Web Vitals)
Server vs Client Components
- Server Component by default:
"use client"only when necessary - Valid reasons for
"use client": React hooks, browser events, local state - Never fetch in a Client Component if avoidable
Suspense+loading.tsxon all routes with data fetching
Core Web Vitals targets
| Metric | Target | Critical |
| LCP (Largest Contentful Paint) | < 2.5s | > 4s |
| CLS (Cumulative Layout Shift) | < 0.1 | > 0.25 |
| FID/INP (Interaction to Next Paint) | < 200ms | > 500ms |
Images
next/imageon all images, never native<img>priorityon the LCP image (above the fold)sizesconfigured according to the actual layout- WebP/AVIF format (automatic via Next.js)
placeholder="blur"on non-critical images
Caching
fetchwith{ cache: 'force-cache' }for static datarevalidateconfigured for semi-dynamic dataunstable_cachefor expensive DB queries- No
no-storeby default unless truly dynamic
Metadata & SEO
generateMetadata()on every page (unique title + description)opengraph-image.tsxorog.pngfor social cardssitemap.tsgenerated dynamicallyrobots.tsconfigured- Structured data (JSON-LD) on product/article pages
Bundle & Performance
next/dynamicfor heavy components (editors, charts, maps)next/fontfor fonts (no external Google Fonts CDN)- Bundle analyzer run (
ANALYZE=true npm run build) if bundle > 500KB - Tree shaking verified on large packages (lodash → lodash-es, etc.)
Output format
## Next.js Review: [page/feature]
### Estimated Core Web Vitals
- LCP: [value / target]
- CLS: [value / target]
- INP: [value / target]
### 🔴 Blocking
### 🟡 Important
### 🟢 Suggestions
### Code optimizations
[corrected code excerpts]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

