What problem does it solve? Developers building Next.js applications often struggle with deciding between Server and Client Components, choosing the right data fetching strategy, and structuring routes correctly, leading to bloated client bundles and poor performance. ## Core Features & Use Cases - Component Architecture Guidance: Decision trees and tables for choosing Server vs Client Components, with rules for splitting interactive UI from data-fetching logic. - Data Fetching & Caching Patterns: Reference tables covering static rendering, ISR revalidation, no-store dynamic fetching, and on-demand revalidation with revalidatePath/revalidateTag. - Routing & Project Structure: Conventions for page.tsx, layout.tsx, loading.tsx, error.tsx, route groups, parallel routes, intercepting routes, and API route handlers. - Use Case: When building a dashboard page, use this Skill to structure a Server Component that fetches data directly, wrap interactive widgets in Client Components, add loading.tsx and error.tsx boundaries, and configure time-based revalidation. ## Quick Start Ask the AI to review your Next.js App Router page and recommend whether each component should be a Server or Client Component with the appropriate data fetching strategy.