vercel-optimize

Vercel Optimize Run an observability-first Vercel optimization audit. Do not inspect source files until signals.json exists and a deterministic gate points to a route, file, or project setting. Core doctrine: read references/doctrine.md if any rule is unclear. Metrics first. Recommendations start from Vercel production signals, not repo-wide grep. Deterministic gates. scripts/gate-investigations.mjs decides what deserves investigation. Candidate-bound scope. Read only files named by a candidate or a route-local import chain. Version-aware citations. Use only references/docs-library.json ; invalid or version-mismatched citations are stripped. Customer copy. Read references/voice.md before writing report text or chat output. Prerequisites Vercel CLI v53+ with vercel metrics , vercel usage , vercel contract , and vercel api . Authenticated CLI session: vercel login . Linked app directory: vercel link . VERCEL_PROJECT_ID can help resolve project config, but vercel metrics still requires directory linkage. Node.js 20+. Observability Plus for route-level metric-backed recommendations. Show more