shadcn

To manage shadcn/ui components across multiple repositories, you need centralized project context and operational instructions. This skill coordinates adding, searching, fixing, and styling components by reading project configuration and loading usage documentation.

A components.json file in shadcn/ui defines project configuration for component registries and presets. It triggers skill activation to apply operational instructions, ensuring consistent component usage, documentation, and tooling across the project.

Adding and searching for shadcn/ui component presets involves running initialization commands and switching presets as needed. The skill coordinates these actions by loading operational instructions from project context to manage component registries.

Yes, shadcn/ui works with custom component registries and presets. The skill activates when working with registries or any project containing a components.json file, supporting triggers like creating an app with a preset or switching to a new one.

Fixing and debugging shadcn/ui styling issues is handled by loading operational instructions from the project's skill context. It coordinates component fixes, debugging actions, and styling adjustments while maintaining consistent documentation across repositories.

Yes, a components.json file is required for shadcn/ui management features. The skill ensures activation by locating project configuration files, reading YAML frontmatter for discovery, and loading Markdown instructions for component actions.