recomponentize-ui

Run the recomponentize step to sort components into atoms, molecules, organisms, and templates with downward-only imports. Vendored registry code stays flat in ui/ and blocks/, while app components are placed at the lowest layer that fits their complexity.

Configure a registries block in components.json with your namespace and token, then inventory local components and map each concept to upstream items using shadcn search and the docs gallery. Install matches with npx shadcn add and rewrite call sites, never the vendored files.

Yes. Without a registry it falls back to stock shadcn, an existing UI library like MUI or Chakra, or a recomponentize-only pass with no new dependencies. The atomic refactor and token codemods run in every case.

The CLI only expands the plain ${VAR} form, so ${VAR:-default} ships as a literal header string. Also the .env file must sit next to components.json, not the repo root, or export the token in the shell instead.

No. Vendored files are overwritten by the next shadcn add, so local edits are silently reverted. Instead compose around them, pass className which merges via cn(), or change the component upstream and re-add it.

Do not run it on a producer repo that publishes the design system itself, since it would invert the pipeline by consuming its own output. Also avoid forcing upstream matches for components with no real equivalent; keep those local and recomponentize only.