shadcn/ui Registry Builder

A custom registry lets you host your own shadcn/ui-compatible components that can be installed with the same `npx shadcn@latest add` CLI command. Instead of publishing to npm, you host a JSON file describing your component — its files, dependencies, and configuration. Teams use custom registries to share design system components across multiple projects.

registry:ui is for primitive UI components (buttons, inputs, cards) that are installed into your components/ui/ folder. registry:component is for more complex, opinionated components that use registry:ui primitives. registry:block is for full page sections or layouts. registry:lib is for utility functions. registry:hook is for React hooks.

Host it as static JSON files on any CDN or web server. Common options: (1) Vercel — deploy a Next.js app that serves the JSON, (2) GitHub Pages — push JSON files to a gh-pages branch, (3) Cloudflare Pages — cheap and fast global CDN, (4) Your own domain with a /r/ path (e.g. yoursite.com/r/component-name.json). The URL just needs to return valid JSON.

registryDependencies lists other shadcn/ui components your component depends on. When a user installs your component, the CLI automatically installs these dependencies too. For example, if your data-table uses a Button component, list 'button' in registryDependencies. Use the official shadcn/ui component names (lowercase slugs).

Yes. Set up one registry package in your monorepo (e.g. packages/ui/registry/) and have all apps reference it. You can serve it locally during development with `npx serve ./registry` and use a deployed URL in production. The CLI also supports local file:// URLs for development.