What problem does it solve?
It helps developers catch and prevent common Next.js App Router mistakes before they reach production, including incorrect file conventions, invalid server and client component boundaries, broken async request handling, and fragile routing or deployment choices.
Core Features & Use Cases
- File and Route Conventions: Validate App Router structure, special files, route groups, parallel routes, intercepting routes, and proxy or middleware naming.
- Server and Client Boundaries: Spot invalid async client components, non-serializable props, and misuse of server-only APIs or directives.
- Data, Metadata, and Error Patterns: Guide correct use of server components, server actions, route handlers, generateMetadata, suspense boundaries, error pages, image optimization, font optimization, bundling, and self-hosting patterns.
- Use Case: A developer can ask it to review a dashboard route tree and quickly identify where params need to be awaited, where Suspense is required, and where a route handler should replace a client-side fetch.
Quick Start
Ask the skill to review your Next.js codebase for App Router correctness, data fetching patterns, metadata, and deployment-safe best practices.