vamosUI
Docs

CLI & registry

Install the whole kit as a package, or copy single components into your project.

Package or copy

npm packageCopy (registry)
Installpnpm add @vamos-cms/uiOne component at a time
UpdatesBump the versionRe-add, or diff with the vamos CLI (planned)
CustomiseProps, tokens, classNameEdit the source freely
Best forTeams that want a maintained kitProjects that need to diverge

Registry Coming with v0.2

Every component and block is published as a registry item at https://ui.vamos.ist/r/<name>.json. The CLI reads it:

npx vamos-ui add button

The item brings its dependencies and the shared token stylesheet the first time.

Registry item format

Each item is a small JSON file: its files, npm dependencies, other items it needs, and the axes it supports.

{
  "$schema": "https://ui.vamos.ist/schema/registry-item.json",
  "name": "button",
  "type": "registry:ui",
  "dependencies": ["radix-ui", "class-variance-authority", "lucide-react"],
  "registryDependencies": ["https://ui.vamos.ist/r/tokens.json"],
  "files": [{ "path": "ui/button.tsx", "type": "registry:ui" }],
  "meta": { "vamos": { "version": "0.1.0", "axes": ["theme", "material", "accent", "density", "font"] } }
}

The vamos CLI Planned

A small CLI on top of the same registry:

npx vamos-ui init            # pick axis presets, write globals.css and the layout boot script
npx vamos-ui add data-table  # copy a component and its dependencies
npx vamos-ui diff button     # show what changed upstream since you copied it
npx vamos-ui upgrade button  # three-way merge upstream changes into your edited copy
Why diff matters
Copied components usually stop receiving fixes. vamos-ui diff and vamos-ui upgrade record the version you copied, so accessibility and bug fixes can still reach your edited code.
PreviousLocalizationNextBlocks