What problem does it solve? Adopting Next.js Cache Components floods a project with blocking-prerender and instant-validation errors, and developers struggle to sequence the migration, choose between opting routes out with export const instant = false versus fixing them in place, and verify that routes actually stream correctly at runtime. ## Core Features & Use Cases - Guided adoption strategies: Choose between an incremental path (run the cache-components-instant-false codemod to opt every route out, ship a passing build, then adopt feature-by-feature) or a direct path (fix blocking routes as the build surfaces them). - Systematic blocker resolution: Diagnose and fix the three blocker classes — request-time reads (cookies(), headers(), await params), sync-IO calls (Date.now(), Math.random()), and "use cache" files reading request data — using the docs page linked from each error. - Runtime verification loop: Verify each fix with next dev plus a browser (via the next-dev-loop skill), not just a passing build, confirming static shells render and <Suspense> fallbacks resolve. - Use Case: A team upgrades to Next.js 16.3, flips cacheComponents: true, and faces dozens of build errors; this skill walks them route-by-route to a clean build with partial prerendering. ## Quick Start Ask the AI to enable Cache Components in your Next.js app and work through the resulting blocking-route errors one feature at a time.
