What problem does it solve? Next.js evolves rapidly, and developers frequently write outdated Pages Router patterns, miss async API changes in Next.js 15/16, or misuse Server Components, leading to build errors, hydration mismatches, and broken deployments. ## Core Features & Use Cases - Pattern Validation: Detects deprecated APIs like getServerSideProps, next/router, next/head, and synchronous cookies()/headers() calls, with severity-ranked migration guidance. - App Router Expertise: Covers routing, layouts, Server Components, Server Actions, route handlers, metadata, image/font optimization, parallel routes, and error handling through dedicated reference docs. - Skill Chaining: Automatically routes related concerns to specialized skills for middleware/proxy, auth, caching, storage, and AI gateway patterns. - Use Case: When migrating a Next.js 14 project to Next.js 16, the skill flags middleware.ts for renaming to proxy.ts, unawaited params/searchParams, and legacy Pages Router files, then provides corrected code patterns. ## Quick Start Ask the assistant to review your Next.js app directory for App Router best practices and Next.js 16 migration issues.