nextjs-developmentlisted

# Next.js Development Installed code wins. Current official documentation for the installed Next.js and React versions wins over remembered syntax, defaults, and this skill. App Router semantics—especially caching, request APIs, Proxy/Middleware conventions, Server Functions, runtimes, and adapters—are volatile; retrieve them before changing those surfaces. ## Scope and triggers Use this skill for App Router architecture and implementation: - `app/` routes, layouts, route groups, special files, and navigation; - Server and Client Component boundaries; - server data reads, streaming, cache policy, and revalidation wiring; - Route Handlers and Server Actions/Functions; - forms and route-level loading, expected-error, exception, not-found, and redirect behavior; - metadata implementation, environment boundaries, runtime choice, instrumentation hooks, output mode, and framework bundle work. Do not use it for Pages Router migration from memory. Inspect the existing router and retrieve the installed version's migration guide before a cutover. Do not turn a Next.js task into a generic React tutorial. ## Ownership and handoffs This skill owns **Next.js implementation boundaries**, not every decision inside them: | Need | Owner | |---|---| | End-to-end stack routing and evidence gates | `full-stack-development` | | Product/operator workflow, roles, lifecycle, and screen contracts | `admin-product-ux` | | Admin information architecture and presentation | `admin-dashboard` |