Installation

No package to install. Each component is a self-contained registry item at /r/[name].json. The CLI fetches it; the source is yours to keep.

Generated code lands under components/lazy-ui. Rename it, restyle it, fork the interaction — nothing hides behind a bundle.

These drop into an existing shadcn-compatible React app. If shadcn/ui is already wired up, you have everything you need.

• A React app with Tailwind CSS configured (Next.js, Vite, or similar).
• shadcn/ui initialized — the cn() helper and components path alias.
• Run the CLI from the project root so generated file paths resolve.

Open a component page, copy its registry URL, pass it to the shadcn CLI. Internal dependencies — a shared util another component needs — are fetched for you.

• Browse every component from the sidebar — each page links to its slug.
• WebGL backgrounds and motion primitives declare their npm deps in the registry item — the CLI installs them with the component.
• Commit the generated files. This is copy-and-paste by design.

Nothing auto-updates — that's the trade-off for owning the source. Re-run the CLI with the same URL to overwrite, or merge changes by hand.

• Re-running shadcn add will prompt before overwriting an existing file.
• Diff against the registry source on GitHub to see what changed.
• Once you've customized a component heavily, treat it as your own code.