Description
next-cache-components-adoption is an agent skill from the Vercel Next.js repository, listed on skills.sh. It turns on Cache Components in a Next.js app and works through the blocking routes it surfaces until the build passes. The skill sequences the work, and the per-error recipes live in the dev overlay and the build output. It applies only to App Router projects, since Cache Components is an App Router feature, and it stops if the project has only a pages tree. The skill also checks that the app can actually boot, because verification runs against next dev in a browser. It requires Next.js 16.3 or later, and it says to upgrade first with the official codemods if the version is older. Before enabling the feature it inventories the dynamic, revalidate and fetchCache exports, which make cacheComponents fail, and follows the migration guide for each. A skill is a SKILL.md file of instructions that an AI agent loads when a task calls for it. It is free and open source, and the skills.sh listing shows all three security audits passing.…
Highlights
- Enables Cache Components and fixes blocking routes
- Requires App Router and Next.js 16.3+
- Inventories incompatible exports first
- Verified in next dev and a browser
Ratings & Reviews
No ratings yet
Be the first to rate next-cache-components-adoption.
People also visit
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes
next-cache-components-adoption FAQ
What does the next-cache-components-adoption skill do?
It enables Cache Components in a Next.js app and works through the routes that block the build until it passes.
Which Next.js version is needed?
Next.js 16.3 or later. Older versions should be upgraded first with the official codemods.
Does it work with pages routers?
No. Cache Components only works for App Router routes, and a pages-only project is out of scope.
What breaks the setting?
Files that still export dynamic, revalidate or fetchCache, which need to be inventoried and migrated first.
How do I install it?
Run: npx skills add https://github.com/vercel/next.js --skill next-cache-components-adoption
What are the best next-cache-components-adoption alternatives?
Popular alternatives to next-cache-components-adoption include next-partial-prefetching-adoption, content-hash-cache-pattern and frontend-a11y. See all next-cache-components-adoption alternatives