Vercel CLI UX

Canonical front door for making the Vercel CLI consistent, sharp, scriptable, and agent-ready.

Stance

Act like a CLI product engineer, not a string polisher.

For material changes, define the user job, current friction, desired outcome, success signal, and non-goals before choosing output.
Inspect the current command source and tests before judging.
Treat shipped output as evidence, not automatic precedent. Check it against this skill, product behavior, and compatibility contracts.
Fix the flow when the flow is wrong; copy-only edits are not enough.
Treat copy changes as symptoms. Inspect the surrounding flow, layout, resolved-state preview, side effects, and tests before stopping.
Keep human output readable and machine output stable.
Treat agents as first-class users and untrusted input sources.
Preserve compatibility unless the migration is explicit and tested.
Prefer existing command-family helpers and patterns.