Menu

Individual skill

vercel-edge-and-isr

0upvotes

Choose a rendering, runtime, and caching strategy on Vercel - Fluid Compute as the default runtime (Edge Functions are deprecated), ISR/PPR, Next.js 16 Cache Components ('use cache', cacheLife, cacheTag, updateTag, revalidateTag), and the Vercel Runtime Cache API (getCache, expireTag, invalidateByTag) with tag-based invalidation. Use when someone asks "should this page be static or server rendered on Vercel", "how do I set up ISR in Next.js", "revalidate this page on demand", or "why is my Vercel page serving stale content" - including streaming vs PPR decisions, caching an API response across regions, and migrating off unstable_cache. Do NOT use to set env vars (use vercel-env-management), wire git/preview/promote deploys (use vercel-deploy-pipeline), route LLM calls (use vercel-ai-gateway), or block bots/rate-limit (use vercel-firewall-and-botid). For pure Core-Web-Vitals/bundle tuning, hand to next-on-vercel-perf.

skills/vercel-edge-and-isr/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Vercel Rendering and Caching

This is the rendering-and-caching stage of shipping a Next.js app on Vercel. By the
time you are here the project deploys (vercel-deploy-pipeline) and its env vars are
set (vercel-env-management); now you decide, per route, **where it runs**, **how it
renders**, and **how long its output lives** - then you make invalidation
deliberate instead of accidental. Wrong defaults here are the difference between a
site that serves from cache in single-digit milliseconds and one that re-runs a
function on every request and still serves stale data.

The single most common mistake is carrying forward advice from the platform's
earlier era. Two defaults flipped: **Edge Functions are deprecated** - Fluid
Compute (full Node.js) is the default runtime - and **`unstable_cache` is
replaced** by Next.js 16 Cache Components. This skill encodes the platform
Back to top