What problem does it solve? Next.js 15/16 introduced breaking changes like async request APIs, the middleware-to-proxy rename, and strict RSC boundaries, and developers frequently ship invalid patterns such as async client components, non-serializable props, hydration mismatches, and data waterfalls. ## Core Features & Use Cases - RSC Boundary Validation: Detects invalid async client components and non-serializable props (Date, Map, class instances) passed across server/client boundaries. - Modern API Guidance: Covers async params/searchParams/cookies/headers, error handling with redirect/notFound/forbidden, route handlers vs Server Actions, and parallel/intercepting route modal patterns. - Performance & Optimization: Enforces next/image, next/font, next/script usage, Suspense boundaries, bundle analysis, and self-hosting setups with standalone output and cache handlers. - Use Case: When reviewing a Next.js pull request, apply these rules to catch a client component receiving a Date prop, a missing default.tsx in a parallel route slot, or a GET route handler conflicting with page.tsx. ## Quick Start Review my Next.js app router code for best practice violations and suggest fixes.