What problem does it solve? Building or migrating Next.js 16 applications requires navigating major breaking changes from v15—middleware.ts replaced by proxy.ts, Webpack removed in favor of Turbopack, Partial Prerendering replaced by the use cache directive, and async params/searchParams—while applying correct App Router and React 19 patterns. ## Core Features & Use Cases - v15 to v16 Migration Guidance: Documents every breaking change including proxy.ts replacing middleware.ts, Turbopack-only builds, and required React 19, with codemod commands for automated upgrades. - Core Framework Patterns: Covers App Router file conventions (page.tsx, layout.tsx, loading.tsx, error.tsx), Server Components, Cache Components (use cache, cacheTag(), cacheLife(), revalidateTag()), and route protection with proxy.ts on the Node.js runtime. - SOLID Module Architecture: Enforces a structure where thin app/ pages import from feature modules (modules/public, modules/auth, modules/cores) for maintainable codebases. - Use Case: Migrating a Next.js 15 dashboard to v16—rename middleware.ts to proxy.ts, switch caching to use cache with tags, await dynamic route params, and validate the result with the sniper agent. ## Quick Start Ask the agent to build a new Next.js 16 page with Server Components and cached data fetching, or to migrate an existing Next.js 15 route to the v16 conventions.
