Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing…
Install
npx skills add vercel/next.js --skill next-cache-components-adoptionnpx skills add vercel/next.js --skill next-cache-components-adoption -a claude-code -gnpx skills add vercel/next.js --skill next-cache-components-adoption -a codex -ggemini skills install https://github.com/vercel/next.js.git --path skills/next-cache-components-adoptiongh skill install vercel/next.js next-cache-components-adoptiongit clone --depth 1 https://github.com/vercel/next.js /tmp/vercel__next.js
mkdir -p ~/.claude/skills ~/.agents/skills
cp -R /tmp/vercel__next.js/skills/next-cache-components-adoption ~/.claude/skills/next-cache-components-adoption # Claude Code
cp -R /tmp/vercel__next.js/skills/next-cache-components-adoption ~/.agents/skills/next-cache-components-adoption # Codex, Cursor, Gemini CLI, Copilot, OpenCode