Bridge Registry

shadcn-compatible CLI bridge registry.

Quinkit registry files are public JSON URLs that generate local bridge files importing from @quinkit/ui without duplicating component logic.

Step 01

Bridge Registry Concept

The Quinkit UI bridge registry serves public JSON schemas compatible with shadcn CLI. Instead of copying 500 lines of unmaintained code into your codebase, bridge files import pre-compiled primitives directly from `@quinkit/ui`.

Step 02

Registry Index Manifest

The registry index contains metadata for all 39 component primitives, specifying dependencies, styles, and export aliases.

Step 03

CLI Component Installation

Run `npx shadcn@latest add` with the component JSON URL to generate a local bridge wrapper file inside `components/ui/`.

1. Add Component via shadcn CLICLI Command
bash
npx shadcn@latest add https://quinkit-ui.vercel.app/r/button.json
2. Generated Local Bridge File (`components/ui/button.tsx`)Generated TypeScript
tsx
// components/ui/button.tsx
// Generated via Quinkit UI Bridge Registry
export { Button, buttonVariants, type ButtonProps } from "@quinkit/ui";
3. Registry Index EndpointPublic JSON URL
txt
https://quinkit-ui.vercel.app/r/index.json
Current Capabilities
  • Instant integration with shadcn CLI tools.
  • Zero component code duplication in client apps.
  • Automatic updates via `@quinkit/ui` package version bumps.
  • Supports all 39 atomic, molecular, and organizational components.
Future Source-Registry Roadmap
  • Optional un-minified raw source code extraction (`--src` flag).
  • Custom AST component tree customization.
  • Local file overrides without package dependency.