nextjs-conventions

To enforce Next.js 15 App Router conventions during a code review, check for default server components usage, explicit 'use client' boundaries, proper server actions, and type-safe TypeScript patterns. This ensures codebase consistency and anti-pattern mitigation.

You should use 'use client' directives in Next.js App Router to explicitly define client component boundaries only when client-side interactivity is required. Components default to server components otherwise, optimizing data fetching and security.

Best practices for data fetching and caching in Next.js 15 involve utilizing server components for default data retrieval and applying explicit caching and revalidation rules. This approach optimizes performance and maintains safety across your application.

Yes, you can use this to standardize TypeScript patterns in a new Next.js project. It applies type-safe patterns to app routing, route handlers, and component organization, improving code quality and onboarding for Next.js applications.

Server actions and route handlers in Next.js 15 work by processing server-side logic and API interactions within the App Router. They enforce type-safe patterns and standard directory structures for secure, optimized data mutations and requests.

Explicit boundaries for server and client components in Next.js are needed to separate server-side data fetching and security from client-side interactivity. This prevents anti-patterns, optimizes performance, and maintains clear component organization.