Installation
Vibra items are installed by the shadcn CLI, straight into your repository. Configure the registry once and every item is one command away.
Set up shadcn/ui
Skip this if your project already has a components.json.
Register the namespace
Add a registries entry to components.json. Everything else in that file stays as it is, and the {name} placeholder is filled in by the CLI.
Add an item
Anything in the catalog can now be installed by name. Dependencies — Vibra’s own primitives, the few shadcn ones it leaves as they are, and npm packages alike — come along with it.
Vibra’s primitives keep shadcn’s names — button, card, input — and shadcn init has already written shadcn’s button, so the CLI asks before replacing it. Answer yes, or pass --overwrite, to take Vibra’s: every component here is drawn against them.
Install without the namespace
Every item is also a standalone registry file. Pass its URL to the CLI and no configuration is needed at all — useful for trying one item, or in a project you do not own.
Copy by hand
Every component page lists its source files under Source, with the path each one belongs at and a copy button. Paste them into your project, install the npm packages the page lists, and copy the registry items its Dependencies section names the same way — a stat card imports the card and the skeleton, and the delta and the number roll beside them. The CLI does nothing you cannot do yourself; it only does all of it at once.
Components read their colours from CSS variables. If you want Vibra’s palette rather than your own, copy the tokens from Theming.
Host your own copy
A copy served from an origin of your own — within what the license allows — needs NEXT_PUBLIC_SITE_URL set to that origin before it is built: it is the origin written into every item’s dependency URLs, so with the local default those dependencies resolve against whoever installs them rather than against your copy.