Home/Registry guide
FLOURISH REGISTRY

Source lands
right in your project.

Every component is a shadcn registry item. One command copies the full, editable source into your codebase — no abstraction layers, no hidden internals.

50COMPONENTS
1COMMAND
0LOCK-IN
QUICKSTART

Add any component in one command.

pnpm dlx shadcn@latest add https://flourish-ui.vercel.app/r/<component>.json

Replace <component> with a component slug, such as skiper39. Its source lands in components/flourish/.

HOW IT WORKS

Three steps. Then it's yours.

  1. 01

    Initialize shadcn

    Run once in a React or Next.js project. Scaffolds the components folder and config file.

    pnpm dlx shadcn@latest init
  2. 02

    Pick a component

    Open any component page, copy its one-line install command, and run it from your project root.

    pnpm dlx shadcn@latest add <url>
  3. 03

    Make it yours

    Source lands directly in your codebase. Edit markup, motion, and styling without limits.

    components/flourish/<component>.tsx
DEPENDENCIES & HELP

Clear setup,
fewer surprises.

Every component page lists required packages before you install. The CLI adds registry files — install any listed external packages separately.

Browse components

Troubleshooting

The command cannot find shadcn

Initialize your project first with shadcn@latest init. No global install needed — dlx handles it.

A package is missing after install

Check the component's Dependencies section and copy the package install command for your package manager.

The import path is different in my app

Keep the generated component where it was installed, or update its import aliases to match your project's components.json.

Can I install multiple components at once?

Not yet via the registry, but each component is fully self-contained. Install them sequentially and they'll coexist cleanly.

OPEN SOURCE, FULLY YOURS

Every piece is a starting point.
Take it somewhere new.

Explore the full library