@vitra/cli
v1.0.0-rc.6
Published
Vitra Image Creator CLI — brand-kit-aware image generation, editing, translation, resize, and campaign orchestration from the terminal. Wraps @vitra/image-creator-node's agent surface with interactive prompts for clarification gates. See docs/superpowers/
Readme
@vitra/cli — vitra
CLI for the Vitra Image Creator. Same backend, same tool surface, and same
credential as the MCP server (@vitra/image-creator-mcp) and the SKILL.md
drop-in. Use the CLI for headless scripting, CI, or just-the-terminal.
Spec: docs/superpowers/specs/2026-05-12-animoca-skill-pack-v4-canonical.md.
Install
npm i -g @vitra/cli
vitra login # paste your vitra_sk_live_* secret
vitra doctor # verify credential, channel, manifestMR-1 commands (this MR)
vitra login | logout
vitra config get | set <key> [value] [--push|--pull]
vitra doctor [--managed-equivalent]
vitra brand-kit create --url URL
vitra brand-kit list
vitra brand-kit get ID
vitra brand-kit update ID [--name "..."] [--voice "..."] [...]
vitra brand-kit delete ID
vitra brand-kit versions IDSubsequent MRs add image.*, asset.search, account.*, campaign.*,
webhooks.*, audit, dev (sandbox). See the v1 plan.
Credential
~/.vitra/credentials.json (mode 0600). Env override: VITRA_HMAC_SECRET.
vitra config syncs ~/.vitra/config.json with the server-side config
store at GET /api/skill/config — --push writes local → server,
--pull writes server → local. This is how a tenant admin can set
auto_approve_when policies once and have every developer's CLI/MCP
pick them up.
--json flag
Every command supports --json for scripting:
vitra brand-kit list --json | jq '.data[] | select(.name == "Animoca Core")'When --json is set, the CLI does NOT prompt interactively — it returns
the needs_clarification envelope as JSON and exits. Useful for shell
pipelines and CI.
Interactive prompts
Without --json, the CLI handles needs_clarification envelopes via the
prompts library: numbered select,
multi-checkbox, text input with validation, etc. Render contracts per
each of the 10 clarification kinds land in MR-2 and MR-4.
MR-1 status
Scaffold. The full commander tree, the prompts-driven clarification
loop, and the 9 MR-1 commands land in subsequent commits to this branch.
License
(TBD — set during MR-12 GA cutover.)
