shadcn

Manage shadcn/ui components across projects with CLI workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fisiohome/monolith --skill shadcn-fisiohome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/fisiohome/monolith/tree/main/.agents/skills/shadcn
Command: npx skills add https://github.com/fisiohome/monolith --skill shadcn-fisiohome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and standardizes the management of shadcn/ui components within a project, reducing drift between registries, presets, and local implementations while improving consistency and maintainability.

Core Features & Use Cases

  • Orchestrates adding, searching, viewing, and updating shadcn/ui components across registries and local projects.
  • Provides project context awareness (framework, aliases, Tailwind version, and registry resolutions) to guide correct usage and imports.
  • Encourages safe, smart updates with documentation fetch, diffing, and optional smart-merge workflows to preserve local changes.

Quick Start

Invoke the shadcn management workflow in your project to add, search, update, or view components and presets with the CLI.

Frequently Asked Questions about shadcn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add shadcn/ui components to an existing project?

Adding shadcn/ui components is orchestrated via the CLI, which reads your project context like framework and Tailwind version to guide correct imports and registry resolutions.

Can I safely update shadcn/ui components without losing local modifications?

Safe updates for shadcn/ui components use documentation fetch, diffing, and optional smart-merge workflows to preserve local changes while reducing drift between registries and local implementations.

How does shadcn/ui manage project context and aliases during initialization?

shadcn/ui initialization extracts project context including framework, aliases, Tailwind version, and registry resolutions to standardize component management and ensure correct usage.

What is the best way to resolve drift between shadcn registries and local component implementations?

Centralizing shadcn/ui component management reduces drift between registries, presets, and local implementations by orchestrating add, search, and update workflows with project context awareness.

Do I need a components.json file to manage shadcn/ui presets and components?

Managing shadcn/ui components applies to projects with a components.json file, utilizing init workflows, presets, and semantic tokens to maintain consistency across local implementations.

Why does shadcn/ui component theming require semantic tokens and variants?

shadcn/ui theming relies on semantic tokens and variants to maintain visual consistency across components, guided by project context extraction and safe merge practices during updates.