component-registrylisted

# Component registry The setup has strong tooling for judging UI after it exists — screenshots, pixel-diff, axe-core, design review. It had nothing for where a component comes from, so every combobox, date picker, and dialog was hand-written from scratch and then critiqued into shape. Registry components have already survived that critique: accessibility, keyboard handling, focus traps, and edge states are solved before you start. ## Protocol 1. **Check the project speaks the protocol.** A `components.json` at the repo root means the shadcn CLI is wired; note its `style`, `tailwind.css`, and `aliases`. No `components.json` in a React + Tailwind repo? `npx shadcn@latest init` is cheap and non-destructive — ask nothing, run it, commit it with the component. 2. **Search before you write.** `npx shadcn@latest search <term>` queries the configured registries; `npx shadcn@latest view <item>` prints the source so you can judge it before adding. Anything `registry.json`-conformant works as a source, not just ui.shadcn.com — a URL or `@namespace/name` both resolve. 3. **Add, then adapt.** `npx shadcn@latest add <item>` vendors the source into the repo — it is yours to edit, not a dependency. Restyle it to the product; do not fork its accessibility wiring (aria attributes, focus management, keyboard handlers) without a reason you can state. 4. **Hand-roll only the gap.** If no registry has the primitive, write it — composed from registry primitives wher