What problem does it solve? Writing and reviewing Next.js code requires keeping track of many evolving conventions—async APIs in v15+, Server/Client Component boundaries, middleware renames in v16, and correct data fetching patterns. This Skill consolidates those rules so code follows current Next.js conventions and avoids common runtime errors. ## Core Features & Use Cases - RSC Boundary Validation: Detects invalid patterns like async Client Components and non-serializable props (Date, Map, class instances) passed across the server/client boundary. - Data Pattern Guidance: Helps choose between Server Components, Server Actions, and Route Handlers, and avoid data waterfalls with Promise.all, Suspense, and preload patterns. - Platform Conventions: Covers file conventions, metadata and OG image generation, image/font optimization, error handling, hydration errors, parallel routes, and self-hosting with Docker. - Use Case: When reviewing a Next.js 15 page that fetches data, the Skill flags synchronous access to params, suggests awaiting it as a Promise, and recommends wrapping useSearchParams consumers in Suspense boundaries. ## Quick Start Review my Next.js page component and apply the next-best-practices rules to fix any async API, RSC boundary, or data fetching issues.
