shadcn-impl-component-install

What problem does it solve?

It prevents broken installs, missing dependencies, and silent overwrites when adding shadcn-ui components across the init → add → customise workflow, especially for long-lived projects that must safely re-run upgrades.

Core Features & Use Cases

• Safe install workflow: guides the correct sequence (init once, add per component, then customise in place) so imported files, aliases, and runtime dependencies stay consistent.
• Alias resolution correctness: helps choose and configure either tsconfig paths or package.json#imports for cn() and component paths, including common Vite multi-file TS config pitfalls.
• Deterministic update strategy: provides a diff-before-overwrite maintenance loop that preserves local customisations and supports targeted manual merges when upstream changes land.
• Decisioning for components vs blocks vs custom registries: determines when to use add <primitive>, add sidebar-07 (blocks), or add @namespace/<name> (private/third-party registries), and how to structure components.json accordingly.
• Anti-pattern avoidance: explicitly blocks common failure modes like running add before init, hand-installing Radix packages, and overwriting without --diff.

Quick Start

Tell your AI: "I’m adding a new shadcn component to an existing project; my app uses Vite/Next with path aliases—walk me through init/add/customise and the exact safe diff-and-overwrite steps for updating without losing my custom variants."