Skip to content
viberdy.dev

Installing from the registry

Every entry in the library is also a shadcn-compatible registry item, which means an AI coding agent — Cursor, Claude Code, Copilot, or the shadcn CLI itself — can install it without a human ever visiting this site. There are three ways to get a component into your project.

1. shadcn CLI, one-liner

Point the CLI straight at a component's registry item URL:

npx shadcn@latest add https://viberdy.dev/r/marquee-ticker.json

2. Add the @viberdy namespace

Register viberdy as a permanent registry in your project's components.json, then install by name going forward:

{
  "registries": {
    "@viberdy": "https://viberdy.dev/r/{name}.json"
  }
}
npx shadcn@latest add @viberdy/marquee-ticker

3. Plain copy-paste

Every detail page has a Code tab with the same source the registry item serves. Copy it directly — no CLI, no install command, no dependency on this site staying up.

Discovery for AI agents

/r/registry.json lists every entry with its tier, tags and category. /llms.txt and /llms-full.txt give an agent a plain-text index and, respectively, the complete source corpus in one request.

Installing Pro components

Free entries install with any of the methods above. Pro entries need an API key so the CLI can prove you have Pro; without one, the registry answers with an upgrade link instead of the file. Set it up once per project:

  1. Create a key on your account page. It is shown once, so copy it straight away.
  2. Add it to your project's .env.local as VIBERDY_API_KEY=vbd_… and never commit it.
  3. Give the namespace a header in components.json:
{
  "registries": {
    "@viberdy": {
      "url": "https://viberdy.dev/r/{name}.json",
      "headers": { "Authorization": "Bearer ${VIBERDY_API_KEY}" }
    }
  }
}

Then install any Pro entry by name:

npx shadcn@latest add @viberdy/booking-slot-picker