shadcn

Run npx shadcn@latest add followed by component names, registry-prefixed names like @magicui/shimmer-button, or GitHub addresses like owner/repo/item. Use --dry-run to preview changes and --diff to compare against existing files before writing.

Run npx shadcn@latest add <component> --dry-run to see affected files, then --diff <file> per file to compare upstream against local. Overwrite files with no local changes and manually merge files you customized; never use --overwrite without explicit approval.

The base field in components.json determines the primitive library and component APIs. Radix uses asChild and type="single"/"multiple" props, while base uses render, multiple booleans, items props on Select, and scalar Slider values.

Pass the preset code directly to npx shadcn@latest apply <code> for existing projects or init --preset <code> for new ones. Never decode codes manually; use preset decode, preset url, or preset resolve to inspect them first.

shadcn rules require flex with gap-* for spacing and semantic tokens like bg-primary or text-muted-foreground instead of raw colors like bg-blue-500. This keeps components themeable through CSS variables and consistent across light and dark modes.

Yes, the CLI supports namespaced registries configured in components.json, public GitHub registries via owner/repo addresses, and registry URLs. After adding third-party items, verify imports match your project's aliases and icon library.