← ClaudeAtlas

next-app-router-patternslisted

Next.js App Router patterns - server/client boundary, data fetching and caching, server actions, streaming, parallel and intercepting routes, edge vs node runtime, and review checklist. Use whenever the project contains a `next.config.*`, an `app/` directory with `page`/`layout`/`route` files, or `next` in `package.json`, OR the user asks about the App Router, server and client components, server actions, or route handlers, even if Next.js is not mentioned by name.
ku5ic/dotfiles · ★ 0 · Web & Frontend · score 72
Install: claude install-skill ku5ic/dotfiles
# Next.js App Router patterns Default assumption: Next.js 16 (current stable as of writing) with the App Router. Pages Router patterns are out of scope. - Cache Components is the new caching model in 16 (opt-in via `cacheComponents: true`); the previous caching model is still supported when the flag is off. - Verify via `package.json` or lockfile - caching model and `cacheComponents` flag differ between 15.x and 16.x. ## Reference files | File | Covers | | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | [reference/anti-patterns.md](reference/anti-patterns.md) | Severity-labeled anti-patterns: cache scoping, server/client boundary, streaming errors | | [reference/server-and-client.md](reference/server-and-client.md) | `"use client"` propagation, server vs client constraints, serialization, `server-only` | | [reference/caching.md](reference/caching.md) | Cache Components vs previous model, `fetch` defaults, segment config, revalidation | | [reference/server-actions.md](reference/server-actions.md) | Server Functions, `"use server"`, form actions, validation, revalidation | | [reference/streaming.md](reference/streaming.md) | `loading.tsx`, `<Suspense>`, err