rule-frontend-app-pages

Next.js App Router pages should use server components by default unless client interactivity is required. This rule enforces standard patterns for page and layout structure, async params typing, and proper error boundaries to maintain a cohesive frontend codebase.

Locale-aware metadata in Next.js App Router is best generated using the generateMetadata() function integrated with translations. This approach avoids hard-coded strings and ensures locale-aware titles and descriptions across your application.

Configuring ISR and dynamic behavior for Next.js App Router pages requires specifying export const revalidate and export const dynamic values. This rule guides developers in properly classifying routes for incremental static regeneration and dynamic rendering.

Yes, this Next.js App Router rule applies to page routes under frontend/src/app including layout/page.tsx, dynamic routes, and locale routing. It covers async params typing, locale routing structure, and proper error and loading boundaries.

Error and loading boundaries in Next.js App Router pages are needed to handle runtime errors and streaming states gracefully. This rule codifies standard patterns for these boundaries to reduce fragmentation and lower maintenance cost.