What problem does it solve? Writing and reviewing Next.js code requires keeping track of many evolving conventions—async APIs in Next.js 15+, Server/Client Component boundaries, middleware renames in v16, and correct data fetching patterns. This Skill consolidates these rules so code follows current Next.js standards and avoids common pitfalls like hydration errors, data waterfalls, and invalid RSC patterns. ## Core Features & Use Cases - RSC Boundary Validation: Detects invalid patterns such as async Client Components and non-serializable props (Date objects, Maps, class instances) passed across the Server/Client boundary. - Modern API Guidance: Covers Next.js 15+ async params, searchParams, cookies(), and headers(), plus the v16 middleware-to-proxy rename. - Performance & Optimization: Rules for next/image, next/font, next/script, bundle analysis, and avoiding data waterfalls with Promise.all and Suspense. - Use Case: When reviewing a pull request that adds a new dynamic route, use this Skill to verify async params handling, metadata generation, error boundaries, and image optimization all follow current Next.js conventions. ## Quick Start Review my Next.js page component and check it against current best practices for async params, metadata, and image optimization.
