What problem does it solve? Modern Next.js development requires constant decisions about server versus client components, data fetching strategies, caching, and routing conventions, and using legacy Pages Router patterns in App Router code causes build errors and runtime bugs. ## Core Features & Use Cases - Architecture Decisions: Provides decision matrices for choosing Server Components, Server Actions, Route Handlers, and runtime targets (Node vs Edge). - Migration Guidance: Maps legacy patterns like getServerSideProps, next/router, next/head, and middleware.ts to their Next.js 16 equivalents such as generateStaticParams, next/navigation, the Metadata API, and proxy.ts. - Validation Rules: Ships pattern-based checks that flag deprecated APIs, un-awaited async request APIs (cookies, headers, params), and boundary violations. - Use Case: When migrating a Pages Router app to App Router, use this Skill to convert data fetching to async Server Components, replace next/head with generateMetadata, and add loading/error/not-found boundaries per route segment. ## Quick Start Ask the agent to review your Next.js app directory and migrate any legacy Pages Router patterns to App Router conventions.