What problem does it solve? Enabling Partial Prefetching in Next.js changes how links prefetch content, and without a structured migration you can silently lose prefetched UI that users relied on. This Skill sequences the entire adoption: auditing Link prefetch behavior, locking in a legacy baseline, opting routes in, enabling the flag, and sweeping for URL-data insights. ## Core Features & Use Cases - Link prefetch audit: Enumerates every <Link prefetch={true}> and router.prefetch() call across the source tree and decides which prefetched UI must be preserved. - Test-backed preservation: Builds a production-mode Playwright rig using @next/playwright's instant() helper so the legacy prefetched UI is locked in as a passing flag-off baseline before any migration edits. - Guided rollout and insight sweep: Adopts routes with export const prefetch = 'partial', enables the global flag, runs the remove-partial-prefetch codemod, then sweeps dev-mode insights like instant-shell-url-data. - Use Case: A team on Next.js 16.3 with Cache Components enabled wants to turn on partialPrefetching without regressing their dashboard navigation; the Skill audits their links, writes preservation tests, migrates each route, and verifies instant navigations against a production build. ## Quick Start Ask the agent to adopt Partial Prefetching in your Next.js app, starting with an audit of all Link prefetch usage and a flag-off preservation baseline.
