next-best-practices

Apply these rules when writing or reviewing Next.js code. See file-conventions.md for: Detect invalid React Server Component patterns. See rsc-boundaries.md for: Next.js 15+ async API changes. See async-patterns.md for: See runtime-selection.md for: See directives.md for: See functions.md for: See error-handling.md for: See data-patterns.md for: See route-handlers.md for: See metadata.md for: See image.md for: See font.md for: See bundling.md for: See scripts.md for: See hydration-error.md for: See suspense-boundaries.md for: See parallel-routes.md for: See self-hosting.md for: See debug-tricks.md for: - Project structure and special files - Route segments (dynamic, catch-all, groups) - Parallel and intercepting routes - Middleware rename in v16 (middleware → proxy) - Async client component detection (invalid) - Non-serializable props detection - Server Action exceptions - Async params and searchParams - Async cookies() and headers() - Migration codemod - Default to Node.js runtime - When Edge runtime is appropriate - 'use client' , 'use server' (React) - 'use cache' (Next.js) - Navigation hooks: useRouter , usePathname , useSearchParams , useParams - Server functions: cookies , headers , draftMode , after - Generate functions: generateStaticParams , generateMetadata - error.tsx , global-error.tsx , not-found.tsx - redirect , permanentRedirect , notFound - forbidden ,...