What problem does it solve? After upgrading to Next.js 16.2 or 16.3, teams often leave new capabilities unclaimed, keep stale or superseded config flags, and miss silent correctness or security regressions that bundled framework documentation cannot surface for their specific repository. ## Core Features & Use Cases - Tiered repo-state audit: Inspects package.json, next.config.*, turbo.json, CI config, and the app tree, then reports findings ranked across four tiers: correctness/security, stale config, available wins, and test coverage. - Concrete predicates with fixes: Each check pairs a grep/read predicate with severity, a concrete fix, and an explicit confidence caveat when repo state alone cannot prove the finding (e.g., CSP set at the edge). - Vendor-tool routing: Detects when first-party tooling (Instant Insights, @next/playwright's instant() helper, Vercel's Cache Components migration skill) should be used instead of reimplementing it. - Use Case: After bumping a monorepo to Next.js 16.3, run the audit to discover a leftover --webpack flag forfeiting Turbopack, an inert cachedNavigations flag missing its cacheComponents dependency, and a missing .next/** entry in turbo.json build outputs. ## Quick Start Audit this repository for unclaimed Next.js 16.3 features, stale config flags, and correctness issues, then report ranked findings with fixes.
