Ephemeral key-value caching layer that lives in Vercel's edge regions, separate from your framework's cache but accessible from Functions, Middleware, and Builds. The tag-based invalidation is the real win here: you can expire entire groups of cache entries at once without tracking individual keys. It's regional and per-deployment isolated, so production and preview environments don't step on each other. Works framework-agnostic via @vercel/functions, though Next.js 16+ gets special treatment with the `use cache: remote` directive. Watch the distinction between expireTag (Runtime Cache only) and invalidateByTag (nukes CDN plus Runtime plus Data caches). Good for API response caching beyond what your framework handles natively.
npx -y skills add vercel-labs/vercel-plugin --skill runtime-cache --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
microsoft/azure-skills
zxkane/aws-skills
awslabs/agent-plugins
microck/ordinary-claude-skills
microsoft/github-copilot-for-azure
zxkane/aws-skills