Next.js Developer guides Claude through App Router projects: planning routes and layouts, fetching data in server components, mutating with server actions, optimizing images and fonts, and preparing a deployment.
It sets firm rules, such as server components by default, explicit fetch cache options, generateMetadata for every SEO tag and loading and error boundaries on async route segments.
What You Get
- A five-step workflow from route planning to a deployment check
- Examples for a cached server component with Suspense, a server action that revalidates a path and a generateMetadata function
- Reference files for the App Router, server components, server actions, data fetching and deployment
- Rules that keep components on the server by default and require loading.tsx and error.tsx on async segments
- An output template covering app structure, pages, actions, configuration and a note on the rendering strategy
Common Use Cases
- Building a product listing with ISR revalidation
- Adding a form that writes data through a server action
- Setting dynamic titles and Open Graph data with generateMetadata
- Adding streaming with Suspense and loading boundaries
- Preparing a Vercel or self-hosted deployment
What Makes It Unique
The skill takes a position on Next.js choices: App Router only, native fetch with explicit cache or revalidate options, next/image for content images and no client components added only to reach data. Its deployment step has measurable gates, a clean next build and Core Web Vitals checked in Lighthouse.
Under The Hood
The skill is instructions and reference markdown that Claude loads by topic; it ships no scripts. Following it, Claude writes route, component and configuration files in your project and runs next build locally. The code examples fetch from a remote API and write to a database from server actions in your own app, and the deployment step asks for Lighthouse or PageSpeed runs against your site.