01
It starts by itself
next feature to adopt. Runs in Claude Code session.
- ↻ next feature to adopt
grep -rln "TODO: Cache Components adoption" app finds files
vercel · 20K installsNext Cache Components Adoption skill
Runs by itself, next feature to adopt.
One feature adopted per run.
Install the Next Cache Components Adoption skill and make it a habit: follow https://gethabit.dev/skills/vercel/next-cache-components-adoption.md
- 1Copy
- 2Paste into Claude Code, Codex or Cursor
- 3It runs by itself
20K installs143K starsMIT licenceSource on GitHub ↗
Next Cache Components Adoption
by vercel · 20K installs
The skill
The next cache components adoption skill turns on Cache Components in a Next.js App Router app and works through blocking routes feature by feature until next build passes.
Only when you ask.
The habit
One feature adopted per run.
↻ Runs by itselfnext feature to adopt
How the habit works.
You don't have to.
When does it start? How does it check its work? What does it remember?
One run, step by step.
Then it stops.
One feature per run, at most two fix rounds per route.
- 01
Check requires
The agent confirms an App Router project, Next.js 16.3+, a bootable app and no experimental.dynamicIO.
- 02
Choose a strategy
It asks if you want one opt-out PR first or everything on one branch.
- 03
Pre-step
For the PR-first path it runs npx @next/codemod@latest cache-components-instant-false and gets next build passing.
- 04
Install verifier
It adds the next-dev-loop skill for runtime checks unless a real blocker stops it.
- 05
Adopt a feature
It removes opt-outs top-down, fixes each blocker from its docs page and checks siblings.
- 06
Verify
It confirms the static shell renders first and each Suspense fallback resolves.
- 07
Check in
It shows you the routes and asks whether to open a PR or stop; it never commits without your yes.
What it may do.
Nothing more.
It writes only in its own folder and asks you before anything goes out.
- Writes only inapp/**, next.config.ts
- Talks tonextjs.org, github.com
- Sendsnothing
- Your OKIt asks you before anything goes out.
Is it for you?
Use it when it fits.
Read both lists. If the left one sounds like you, the Next Cache Components Adoption skill helps.
Use it when
- ✓ You enable cacheComponents in Next.js
- ✓ The build floods with blocking-prerender errors
- ✓ You want to adopt route by route in small PRs
Skip it when
- – The app only uses the pages router
- – Next.js is below 16.3 and you cannot upgrade
Next Cache Components Adoption skill, answered.
Can I opt routes out for now?
Yes. export const instant = false lets a route block, but sync IO like Date.now() still fails the build.
Why not just use next build?
The build stops at the first blocking route and cannot show what is in the static shell; next dev and a browser can.
How do I install the Next Cache Components Adoption skill?
Copy the prompt at the top into your agent. It installs the skill from vercel/next.js and sets up the habit. Or run npx skills add vercel/next.js --skill next-cache-components-adoption.
Is the Next Cache Components Adoption skill free?
Yes. It is published under MIT. Habit is free too.
Next Cache Components Adoption. Now as a habit.
Install the Next Cache Components Adoption skill and make it a habit: follow https://gethabit.dev/skills/vercel/next-cache-components-adoption.md
All vercel skills →More code skills →
Works in
- Claude Code
- Codex
- Cursor
- ChatGPT
- Claude app
Made by vercel, published under MIT. Habit links to the original and never changes it. Is this your skill?