What problem does it solve? Next.js 15+ introduced breaking changes like async request APIs, stricter Server/Client Component boundaries, and renamed middleware, making it easy to write code that fails at build time, causes hydration errors, or silently degrades performance. ## 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 eliminates data 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 page that fetches data sequentially and passes a Date object to a client component, apply this Skill to refactor it into parallel server-side fetches with serialized props. ## Quick Start Review my Next.js page component and fix any violations of App Router best practices including async params, RSC boundaries, and data fetching patterns.
