What problem does it solve? Frontend teams working with Next.js App Router often struggle with deciding where components should render, how to structure routes, and how to handle data loading without leaking sensitive logic to the client. This Skill provides repo-aligned patterns and review heuristics to keep App Router code consistent, secure, and maintainable. ## Core Features & Use Cases - Server-first architecture guidance: Enforces Server Components by default, with Client Components scoped only to genuine interactivity. - Data loading and mutation patterns: Covers server-side fetching, caching, revalidation, Server Actions, and loading/error/empty states. - Route and feature structure: Guides layouts, parallel routes, intercepting routes, and domain-driven segment organization. - Use Case: When building a new dashboard screen, activate this Skill to structure the route with server-side data fetching, isolated Client Components for interactive widgets, and proper loading and error boundaries. ## Quick Start Ask the assistant to review or scaffold a Next.js App Router page following the repo's Server Components and data-loading patterns.
