vercel-optimize

Run this audit from your linked Vercel project directory. It collects usage and route metrics, applies deterministic gates to find cost drivers like uncached routes, slow functions, and build fan-out, then produces ranked recommendations with verified code fixes.

The Skill queries route-level function duration, invocations, cold starts, and cache hit rates through the Vercel CLI, then gates candidates by thresholds such as p95 over 500ms at meaningful traffic. Only metric-backed routes are investigated in source code.

Next.js App and Pages Router and SvelteKit have full route-to-file mapping, Nuxt gets route mapping with generic checks, and Astro is limited. Hono, Remix, and unknown frameworks pause and require confirmation before a limited platform-only audit.

You need Node.js 20+, Vercel CLI v53 or later, an authenticated session, and a linked project directory via vercel link. Observability Plus is required for route-level metric-backed recommendations; without it the audit pauses or runs a limited code-only mode.

The Skill follows an observability-first doctrine, so it refuses to guess from source files when metrics fail. It reports the specific blocker, such as payment_required, not_linked, or no_traffic, and asks whether to enable Observability Plus or continue with a limited code-only audit.

No. Recommendations use cost magnitude framing instead of precise dollar projections, and all citations come from a curated, version-aware documentation allow-list so invented URLs and mismatched framework advice are stripped.