Adopt Cache Components in your Next.js app
Enable the cacheComponents flag and walk every blocking route to a passing build, incrementally or directly
- What
- Enable the cacheComponents flag and walk every blocking route to a passing build, incrementally or directly
- Cost
- Free
- Needs
- a Next.js 16.3+ App Router project that actually boots (real env/database); upgrade first if below 16.3
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a sequenced migration workflow for turning on Cache Components in a Next.js 16.3+ App Router project: flip the `cacheComponents` flag, inventory incompatible config keys, then walk the route tree top-down — each blocking route fixed in `next dev` with the dev overlay's fix cards, verified in a real browser, and gated by a passing build. Choose the Incremental path (codemod opts every route out first, then un-opt them feature by feature) or the Direct path (fix as the build flags them). By @vercel, listed here with credit to its creator. Honest caveats: requires Next.js 16.3+ and a runnable app (real env/database) — a hybrid `pages/` + `app/` project only migrates its `app/` tree; per-error recipes live in the dev overlay and the official migration guide, which the skill points to as the source of truth; pairs well with the next-dev-loop skill for runtime verification. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Adopt Cache Components is a free migration workflow for turning on Cache Components in a Next.js 16.3 plus App Router project. It flips the cacheComponents flag, inventories config keys, then walks the route tree, with each route fixed in next dev with dev fix cards, verified in a browser, and gated by a build, Incremental or Direct path.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it📌 Pinned version: commit 5da8ef1Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Next.js 16.3+ App Router project that actually boots (real env/database); upgrade first if below 16.3 Install "Adopt Cache Components in your Next.js app" for me. Give my agent the sequenced Cache Components adoption workflow — flip the cacheComponents flag, inventory incompatible config keys, walk the route tree top-down fixing blocking routes in next dev, verify each fix in a real browser, gate every feature on a passing build Repository: https://raw.githubusercontent.com/vercel/next.js/5da8ef12bc6b4156dd490e58e3878e06fd7f4472/skills/next-cache-components-adoption/SKILL.md Pinned version: install the code at commit 5da8ef12bc6b4156dd490e58e3878e06fd7f4472 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the vercel-next.js-next-cache-components-adoption skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "vercel-next.js-next-cache-components-adoption". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. make sure the project runs Next.js 16.3+ with Turbopack and boots locally; optionally install the next-dev-loop skill for runtime verification). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 5da8ef1 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox and failed · Nov 18, 2026 — Needs pnpm, npm cannot install it · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.