V Vultra UI

CLI Workflow

The Vultra CLI installs components directly into your project — copy mode or npm mode.

Install

npx @vultra/cli init

This sets up:

  • components.json — alias config
  • src/lib/utils.ts — cn() helper
  • Token CSS import

Add Components

# Copy mode (shadcn-style) — sources copied into your project
npx @vultra/cli add button card badge

# MD3 + flat components
npx @vultra/cli add fab chip snackbar
npx @vultra/cli add blob-card hexagon-grid diamond-badge

# Npm mode — adds @vultra/ui to package.json instead of copying
npx @vultra/cli add button --mode npm

Copy mode rewrites $lib imports to your project aliases automatically.

Dependency Resolution

The CLI resolves transitive dependencies automatically:

npx @vultra/cli add pagination
# Pulls in: button (pagination uses it)
# Adds deps: clsx, tailwind-merge, tailwind-variants

Component registries are versioned:

  • 155 components across core, md3, and flat packages
  • Embedded file contents — works offline, no monorepo needed

Update

# Update specific components
npx @vultra/cli update button

# Update everything installed
npx @vultra/cli update --all

Doctor

npx @vultra/cli doctor

Checks:

  • components.json exists + aliases valid
  • Token CSS imported
  • Installed components match registry
  • Missing npm dependencies

Browse

# List all components by category
npx @vultra/cli list

# With descriptions
npx @vultra/cli list --verbose

Components.json

{
  "components": "./src/lib/components",
  "utils": "./src/lib/utils.ts",
  "ui": "./src/lib/components",
  "registry": "./registry/index.json"
}

Publishing Components

Components come from the Vultra UI monorepo. The registry generator scans packages/{core,md3,flat}/src/lib/components/ and embeds:

  • File contents
  • Runtime dependencies
  • Props metadata (for tooling)

Next Steps