fumadocs-registry-integration

Register components by creating a registry.json entry with name, type, title, description, registryDependencies, and files fields. This enables the component to be discovered and installed via the shadcn/ui add command.

Registry entries require name, type, title, description, registryDependencies, and files. Each field must follow the consistent, well-formed JSON pattern to ensure proper integration with shadcn/ui's add command.

Update registry.json when releasing new components or staging components for distribution. This ensures they're discoverable and installable through shadcn/ui's component discovery system.

Yes, registry entry creation can be automated by applying the consistent pattern—name, type, title, description, registryDependencies, and files—across multiple component definitions to batch-register them.

Malformed registry.json prevents components from being discovered by shadcn/ui add. Entries must maintain the enforced pattern with proper JSON formatting and all required fields to integrate correctly.

This approach is designed specifically for shadcn/ui registry integration. It creates entries compatible with shadcn/ui's add command and discovery system, following that ecosystem's registry standards.