What problem does it solve? Developers working with Next.js 16+ often face confusion about Turbopack versus webpack behavior, slow dev startup, bundle bloat, and the new proxy.ts middleware filename convention. This Skill provides clear operational guidance so you avoid misconfigurations and incorrect code review flags. ## Core Features & Use Cases - Bundler Selection Guidance: Explains when to use Turbopack (default dev) versus webpack (legacy fallback via --webpack) and how production builds behave across Next.js versions. - Dev Performance Optimization: Covers file-system caching under .next for faster restarts and the experimental Bundle Analyzer in Next.js 16.1+ for trimming heavy dependencies. - Middleware Naming Rules: Clarifies that Next.js 16 uses proxy.ts instead of middleware.ts, preventing incorrect rename suggestions during code review. - Use Case: While reviewing a Next.js 16 project, you notice a proxy.ts file and slow HMR; this Skill tells you the filename is correct and directs you to verify Turbopack caching instead of renaming the file. ## Quick Start Ask the agent to review my Next.js 16 project for Turbopack configuration, dev performance, and correct middleware file naming.
