next-best-practices — Claude Code skill: Next.js rules

What next-best-practices does

The skill kicks in while the agent writes or reviews Next.js code, and tells it what the framework expects. It ships as a bundle of reference files. One covers project layout and the special files, plus dynamic, catch-all and grouped route segments, parallel and intercepting routes, and the middleware rename in v16.

Another set deals with React Server Components: spotting an async client component, non-serializable props, exceptions thrown from Server Actions. Async patterns for Next.js 15+ get their own file — params, searchParams, cookies() and headers() are all async now, and a codemod handles the migration. Runtime choice is short: Node.js unless Edge actually fits.

Error handling has a file of its own (error.tsx, global-error.tsx, not-found.tsx, redirect, notFound, forbidden, unauthorized). Data patterns explain when to reach for a Server Component, a Server Action or a route handler, and how to avoid waterfalls with Promise.all and Suspense. The rest covers metadata and OG images through next/og, next/image and next/font, bundling, scripts, hydration errors, Suspense boundaries, and self-hosting with output: 'standalone'. You do not invoke it yourself — it is marked user-invocable: false and loads on its own when the context fits.