
Vercel Functions
This is your Vercel compute layer reference. It covers Serverless Functions, Edge Functions, Fluid Compute, streaming responses, and Cron Jobs. The skill's real value is in the validation patterns: it catches Pages Router types in App Router code, flags direct OpenAI/Anthropic SDK usage (suggesting AI SDK instead), warns when you're writing to the local filesystem or using in-memory caches that won't persist, and spots Express.js imports that won't work in serverless. It chains to workflow guidance when it sees setTimeout polling, and to storage skills when you try filesystem writes. The pathPatterns auto-activate it for api/ folders and route.* files. Helpful if you keep forgetting serverless functions are stateless and ephemeral.
- skills.sh installs
- 410
- GitHub stars
- 183
- last updated
- Jun 3, 2026
Install
$ npx -y skills add vercel/vercel-plugin --skill vercel-functions --agent claude-codeInstalls into .claude/skills of the current project.
Files
Vercel Functions
You are an expert in Vercel Functions — the compute layer of the Vercel platform.
Prefer Node.js over the Edge runtime
Strongly prefer Node.js. Don't reach for runtime = 'edge' in new code, and recommend migrating off it when you find it in existing code.
This follows Vercel's own documented guidance — "we recommend migrating from edge to Node.js for improved performance and reliability" — and one hard constraint: as of Next.js 16.3, runtime = 'edge' is no longer supported. Routes and pages there run on Node.js regardless of what you write, so on 16.3+ this stops being a recommendation and becomes a migration you have to do.
Everywhere else it is a strong default, not a prohibition. Both runtimes run on the same Fluid Compute infrastructure, in the same regions, under the same Active CPU pricing — so in nearly every case Edge gains you nothing while costing you most of the Node.js API surface. If you have a specific, tested reason to stay on Edge, that's a legitimate call; just make it deliberately rather than by habit.
The default to reach for
Sponsors
Details
- Repository
- github.com/vercel/vercel-plugin
- Category
- Cloud & Infrastructure
- First seen
- Jun 3, 2026
More from vercel/vercel-plugin
All 25- Next Cache Components385
- Next Upgrade368
- Routing Middleware338
- Auth326
- Vercel Storage326
- Vercel Agent317
- Bootstrap315
- Chat Sdk315
- Verification315
- Workflow313
- Runtime Cache312
- Vercel Sandbox308
- Knowledge Update301
- Marketplace300
- Next Forge191
- Nextjs629
- Ai Sdk544
- React Best Practices491
- Deployments Cicd484
- Shadcn458
- Vercel Cli432
- Turbopack429
- Ai Gateway423
- Env Vars422