
Next Cache Components
This walks you through Next.js 16's new caching model, which replaces the old experimental PPR flag with a cleaner `use cache` directive. You get three content types in one route: static shells that prerender instantly, cached async data with `cacheLife()` for stale-while-revalidate, and dynamic Suspense boundaries for fresh runtime data. The guide covers tagging with `cacheTag()`, invalidation with `updateTag()` versus `revalidateTag()`, and the key constraint that you can't use cookies or headers inside cached functions unless you pass them as arguments. If you're migrating from `unstable_cache` or route segment configs like `revalidate = 60`, there's a conversion table. Solid reference for actually understanding how PPR works instead of cargo culting config flags.
- skills.sh installs
- 704
- GitHub stars
- 950
- last updated
- Jul 14, 2026
Install
$ npx -y skills add vercel/nextjs-skills --skill next-cache-components --agent claude-codeInstalls into .claude/skills of the current project.
Files
This walks you through Next.js 16's new caching model, which replaces the old experimental PPR flag with a cleaner `use cache` directive. You get three content types in one route: static shells that prerender instantly, cached async data with `cacheLife()` for stale-while-revalidate, and dynamic Suspense boundaries for fresh runtime data. The guide covers tagging with `cacheTag()`, invalidation with `updateTag()` versus `revalidateTag()`, and the key constraint that you can't use cookies or headers inside cached functions unless you pass them as arguments. If you're migrating from `unstable_cache` or route segment configs like `revalidate = 60`, there's a conversion table. Solid reference for actually understanding how PPR works instead of cargo culting config flags.
Browse the repository on GitHubSponsors
Details
- Repository
- github.com/vercel/nextjs-skills
- Categories
- Frontend Development, Cloud & Infrastructure
- First seen
- Jun 3, 2026