nextjs-developmentlisted

# Next.js Development > Optimized for Next.js 16+, React 19+, TypeScript 5.5+, Turbopack, and App Router-first architectures. Comprehensive reference for [Next.js](https://nextjs.org/docs) (latest: **16.2.4**) with the App Router, TypeScript, and modern patterns. Covers project structure, Server/Client Components, data fetching, caching with the `use cache` directive, Server Actions, MCP devtools integration, and performance optimization. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Component Review Rubric Reference Apply the shared [Component Review Rubric](../frontend-design/SKILL.md#component-review-rubric) before approving Next.js components, then run the Next.js-specific checks below. ## Anti-Patterns - Mixing server and client responsibilities: Bundle size, caching, and auth decisions become harder to reason about. - Using legacy synchronous request APIs: Modern Next.js expects async request surfaces such as `params`, `headers()`, and `cookies()`. - Skipping route-level loading and error states: Streaming apps feel broken when only the happy path is implemented. ## Verification Protocol Before claiming "skill applied successfully": 1. Pass/fail: The Nextjs Development guidance is tied to a concrete route, component, screen, or design artifact. 2. Pass/fail: Component states cover loading, empty, error, success, and responsive breakpoints where applicable. 3. Pass/fail: Accessibility, visual hierarchy, and interact