LowFile-scopeJavaScript / TypeScript Plug & play

Use Metadata API instead of <Head>

Declare SEO metadata via export const metadata or generateMetadata; avoid manual <Head> in App Router.

Why this matters

Provides consistent, typed SEO that works with RSC.

Side-by-side examples engineers can pattern-match during review.

Avoid

import Head from 'next/head'
export default function Page(){ return (<><Head><title>Title</title></Head></>) }

Prefer

export const metadata = { title: 'Dashboard', description: 'KPIs' }
export default function Page(){ return <main>...</main> }

Bad

<Head> in app/*

Good

export const metadata = { title:'X' }

From the same buckets as this rule.

High
Keep 'use client' at the leaf: default to Server Components
Prefer Server Components for pages/layouts and move interactivity to small leaf Client Components. Only add 'use client' where browser APIs or event handlers are strictly necessary.
stack-nextjsstack-react+2
High
Make fetch caching explicit in Server Components
For dynamic data use { cache: 'no-store' } or file-level dynamic = 'force-dynamic'. For ISR use { next: { revalidate: N, tags: [...] } }.
stack-nextjsstack-react+2
High
Middleware only for light auth/rewrites
Keep middleware fast and side-effect free (no DB writes). Narrow the matcher and skip static assets. Use Route Handlers for heavy logic.
stack-nextjsstack-react+2