What problem does it solve? Adopting Partial Prefetching in a Next.js 16.3+ app requires auditing every <Link prefetch={true}> call, opting routes in with export const prefetch = 'partial', enabling the partialPrefetching flag, and clearing dev-overlay insights — a multi-step migration that is easy to get wrong without a structured process. ## Core Features & Use Cases - Link Prefetch Audit: Enumerates declarative <Link prefetch={true}> and imperative router.prefetch() call sites across the source tree and adopts each destination route. - Insight-Driven Sweep: Drives the running app in a browser to surface and resolve the instant-link-prefetch-partial and instant-shell-url-data insights from the dev overlay and dev log. - Production Verification: Confirms shared App Shells paint on navigation under next build/next start, since prefetching only runs in production. - Use Case: A team on Next.js 16.3 with Cache Components enabled wants to turn on Partial Prefetching; the skill walks them route by route, adds use cache boundaries where prefetched data must be preserved, and hands off a per-link prefetching decision list. ## Quick Start Ask the AI to adopt Partial Prefetching in your Next.js app by auditing the Link prefetch calls and enabling the partialPrefetching flag.
