Install with shadcn CLI

The kit also ships as a shadcn-compatible registry, so you can install components with the shadcn CLI instead of ours. Same source, same components, different distribution.

When to use it

Use the shadcn flow if your project already runs shadcn init and you want every UI source (shadcn primitives, our kit, any third-party registry) installed through one tool. Use the native CLI if you want framework auto-detection, conditional CSS token appending, and dependency assertions out of the box.

Setup

If you haven't already, initialize shadcn in your project. This creates components.json and the path aliases the registry uses.

Then install the base item once. It seeds the design tokens (cssVars), keyframes, and base dependencies.

Namespace (recommended)

Register the kit as a namespace in components.json so you can install by short name.

Then add any component with the namespace prefix.

The file lands at <aliases.components>/ai/message.tsx with imports rewritten to your project's @/lib/utils and @/components/ai/* aliases.

Without a namespace

If you don't want to edit components.json, you can pass the full URL each time.

Transitive dependencies (e.g. composer-rich requiring composer) resolve automatically.