What problem does it solve?
Next.js codebases fail or slow down when developers mix routing paradigms, misuse Server vs Client Components, or rely on deprecated APIs—this Skill helps you implement the correct App Router patterns with fewer regressions.
Core Features & Use Cases
- App Router architecture guidance: Choose correct file conventions and component boundaries for Server Components, layouts, and route segments.
- Modern data and caching patterns: Apply async
params/searchParams, use cookies()/headers() correctly, and follow Next.js cache/caching idioms to avoid runtime issues.
- Migration and deprecation validation: Detect Pages Router patterns (e.g.,
getServerSideProps, next/head, next/router) and guide safe migration to App Router equivalents.
- Vercel-ready routing/runtime ergonomics: Prefer
proxy.ts over middleware.ts in Next.js 16+, and surface common serverless compatibility pitfalls (API handler placement, in-process caches, heavy dependencies).
- Optional deep dives via included references: Leverages a repository of Next.js best-practice docs (file conventions, RSC boundaries, async patterns, route handlers, metadata, suspense boundaries, etc.) for targeted fixes.
Quick Start
Ask the agent to refactor my Next.js Pages Router code to the App Router by removing getServerSideProps and updating metadata, routing, and middleware/proxy usage for Next.js 16.