Agent skill · software engineering · vercel
cli-ux
Use for packages/cli changes that affect command UX, prompts, help, output layout, progress, success, warnings, errors, JSON/stdout/stderr contracts, non-interactive/agent behavior, copy, or tests for those surfaces. Do not load for implementation-only refactors with unchanged CLI surface.
Why this skill is useful
Provides detailed workflows and decision-making frameworks for enhancing CLI user experience that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-06. 16,048 stars on the source repository.
What this skill does
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. Decision Authority Resolve conflicts in this order: 1. The user's explicit goal and constraints. 2. Verified product and system truth: API behavior, permissions, billing, data models, reachable states, and compatibility contracts. 3. Repository-canonical guidance: AGENTS.md, this skill, shared helper contracts, and tests that encode intentional behavior. 4. Accepted command-specific contracts in command-contracts.md. 5. Verified adjacent command-family patterns. 6. General CLI heuristics. Do not let a lower source override a higher one. Shipped code proves what exists, not why it is correct. Workflow 1. Outcome map. For material UX changes, name the user and job, current behavior, desired outcome, success signal, and non-goals. 2. Surface map. List help, flags, prompts, progress, warnings, success, errors, tables/lists, detail views, JSON, and agent/non-interactive payloads. 3. Structure map. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/cli-ux