shadcn

To add shadcn/ui components, run the shadcn CLI with your project package runner. The workflow manages integration by reading your components.json configuration and applying registry-safe presets to ensure accurate component installation.

The best way to compose shadcn/ui forms and dialogs is to follow strict UI guardrails. Enforce correct semantic colors, spacing, and icon usage rules to ensure your overlays and form components remain fully accessible and visually compliant.

shadcn/ui styling breaks when custom Tailwind tokens bypass semantic color rules. Maintain UI correctness by strictly using semantic tokens for colors and gap-* utilities for spacing, ensuring your components map correctly to your preset's design system.

Yes, you can use the shadcn CLI to search registries and fetch documentation. It supports debugging and maintenance by allowing you to preview diffs and apply component updates safely within your current project context.

You need a Tailwind setup configured with semantic tokens and a valid components.json file. shadcn/ui requires this project-aware configuration to properly map styles, enforce layout rules, and manage component composition through the CLI.

Limitations arise when bypassing the shadcn CLI or ignoring semantic token rules. Overlay patterns, icon data attributes, and form composition require strict adherence to preset configurations, meaning manual component additions often break accessibility and styling guardrails.