Vercel Routing

Vercel MCP first for deployments and config; CLI for dev/deploy; Next.js local docs first for framework facts; workflow skills for multi-step agent loops.

Vercel interface ranks: Source: Skill Resolver, 2026-05-31

1. MCP (plugin-vercel-vercel) - deployments, env, logs, domains

2. CLI (vercel) - vercel dev, vercel deploy, vercel env pull, and vercel deploy --dry --format=json before deploy mutations

3. Project-local Next docs / managed AGENTS.md - version-matched framework reference

4. Workflow skills - next-dev-loop, next-cache-components-adoption, next-cache-components-optimizer, AI SDK, shadcn, Turbopack

Next.js 16.3 retired knowledge-only Next skills in favor of local bundled docs and AGENTS.md; use skills for workflows that drive browser/runtime/cache-component loops. Source: Next.js 16.3 AI Improvements, 2026-06-26

Do not fold this routing page into v0 by Vercel. v0 is Vercel's product surface for generated apps and design-system skills; this page owns interface selection for Vercel operations, Next.js facts, and workflow skill routing.

---

Timeline

• 2026-07-02 | Added Vercel CLI dry-run deployments as the required preflight before CLI deploy mutations; use vercel deploy --dry --format=json or repo wrappers such as npm run vercel:dry to inspect framework detection, included files, ignored paths, sizes, file modes, and hashes without creating a deployment. Source: User request, 2026-07-02; Vercel changelog, 2026-07-01
• 2026-06-27 | Clarified that v0 by Vercel is a related product/tool page, not the owner of Vercel interface routing. Source: wiki consolidation pass, 2026-06-27
• 2026-06-26 | Updated Next.js routing: local version-matched docs and managed AGENTS.md own framework facts; first-party skills now own workflow loops such as next-dev-loop and Cache Components adoption/optimization. Source: Next.js 16.3 AI Improvements, 2026-06-26
• 2026-05-31 | Vercel routing from service registry. Source: public wiki expansion, 2026-05-31