
Vercel Functions
This is comprehensive guidance for working with Vercel's serverless and edge compute layer. It covers Serverless Functions, Edge Functions, Fluid Compute, streaming responses, and Cron Jobs. What makes it genuinely helpful is the pattern validation: it catches common mistakes like using the Pages Router API types in App Router, writing to local filesystem (which is ephemeral), or implementing manual retry logic when Workflow exists for that. The chainTo rules are smart about surfacing the right skill when you're doing something better suited elsewhere, like using raw OpenAI SDKs instead of the Vercel AI SDK, or running polling loops that should live in Workflow. Use this when you're building API routes or need to debug why your function is timing out or losing state.
- skills.sh installs
- 259
- GitHub stars
- 183
- last updated
- Jun 3, 2026
Install
$ npx -y skills add vercel-labs/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-labs/vercel-plugin
- Category
- Cloud & Infrastructure
- First seen
- Jun 3, 2026
More from vercel-labs/vercel-plugin
All 32- Chat Sdk257
- Env Vars250
- Vercel Storage244
- Workflow236
- Auth232
- Runtime Cache228
- Verification226
- Vercel Sandbox219
- Next Cache Components218
- Next Upgrade213
- Bootstrap211
- Marketplace208
- Vercel Plugin Eval206
- Plugin Audit198
- Benchmark Agents197
- Release194
- Benchmark Testing193
- Knowledge Update190
- Benchmark E2e187
- Benchmark Sandbox181
- Next Forge158
- Nextjs4.3K
- React Best Practices721
- Shadcn399