What problem does it solve? Next.js developers frequently encounter subtle bugs and anti-patterns: invalid async client components, non-serializable props crossing RSC boundaries, hydration mismatches, data waterfalls, and misconfigured images, fonts, or scripts. This Skill provides a structured rulebook for writing and reviewing Next.js code correctly across App Router conventions, async APIs, error handling, and deployment. ## Core Features & Use Cases - RSC Boundary Validation: Detects invalid patterns like async client components and non-serializable props (Date, Map, class instances) passed from Server to Client Components. - Data Pattern Guidance: Helps choose between Server Components, Server Actions, and Route Handlers, and avoid waterfalls with Promise.all, Suspense, and preload patterns. - Optimization Rules: Covers next/image, next/font, next/script, metadata/OG image generation, bundling fixes, and self-hosting with standalone output and cache handlers. - Use Case: When reviewing a Next.js 15+ page that fetches data sequentially and passes a Date object to a client component, use this Skill to identify the waterfall, fix the serialization issue, and apply async params conventions. ## Quick Start Review my Next.js page component for best practice violations and suggest fixes for data fetching and RSC boundary issues.