shadcn

To manage shadcn/ui components, use the CLI to add, search, fix, debug, style, and compose UI elements within your project. This process relies on your components.json file to maintain consistent configuration and streamline component orchestration across your setup.

A shadcn/ui preset defines a specific configuration for your component registry. You need to switch presets when you want to change your project's styling or component architecture, triggered via CLI actions like creating an app with the --preset flag.

To initialize shadcn/ui, run the `shadcn init` CLI command within your project directory. This action sets up the components.json file and establishes the necessary project context to begin productive UI development.

Yes, this approach works directly with an existing components.json configuration file. The Skill actively detects this file to provide accurate project context, component documentation, and CLI interactions for managing your UI components.

The best way to fix and debug styling issues in shadcn/ui components is by leveraging the project context and component documentation provided by the Skill. This allows you to systematically identify and resolve UI composition and styling problems.

You need a component registry to unify component orchestration and configuration, which reduces boilerplate. It enables consistent workflows for maintaining, adding, and searching UI components across different project setups.