agentleFS
samsam007bsamsam007b/claude-code-standards-kit/skills/nextjs-review/SKILL.md

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.

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
  1. Distinctive:

    Before a production release

    line 12

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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.tsx on all routes with data fetching

Core Web Vitals targets

MetricTargetCritical
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/image on all images, never native <img>
  • priority on the LCP image (above the fold)
  • sizes configured according to the actual layout
  • WebP/AVIF format (automatic via Next.js)
  • placeholder="blur" on non-critical images

Caching

  • fetch with { cache: 'force-cache' } for static data
  • revalidate configured for semi-dynamic data
  • unstable_cache for expensive DB queries
  • No no-store by default unless truly dynamic

Metadata & SEO

  • generateMetadata() on every page (unique title + description)
  • opengraph-image.tsx or og.png for social cards
  • sitemap.ts generated dynamically
  • robots.ts configured
  • Structured data (JSON-LD) on product/article pages

Bundle & Performance

  • next/dynamic for heavy components (editors, charts, maps)
  • next/font for 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]

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.