shadcn

Manage shadcn/ui components, presets, and docs via CLI commands.

5|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Tristan578/project-forge --skill shadcn-tristan578
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/Tristan578/project-forge/tree/main/.agents/skills/shadcn
Command: npx skills add https://github.com/Tristan578/project-forge --skill shadcn-tristan578

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the discovery, configuration, and lifecycle management of shadcn/ui components, presets, and docs across projects.

Core Features & Use Cases

  • Centralized project context via components.json, enabling consistent imports and aliasing.
  • Seamless CLI workflow for init/add/docs/info/view, ensuring uniform component workflows across teams.
  • Support for multiple templates and themes, including preset switching and theming.

Quick Start

Run the shadcn CLI in your project directory to inspect the project context and begin adding needed components from registries.

Frequently Asked Questions about shadcn

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

FAQPage Schema
How do I manage shadcn/ui components across multiple projects?

You can manage shadcn/ui components across projects by utilizing a centralized components.json file for consistent aliasing, enforcing frontmatter-driven metadata, and running CLI commands to ensure uniform workflows.

How do I add shadcn components using the CLI?

You add shadcn components by running the CLI add command in your project directory, which inspects the project context and pulls needed components from registries to ensure safe defaults and uniform integration.

What is the best way to align a design system when bootstrapping new apps with shadcn?

Aligning a design system when bootstrapping new apps involves applying shadcn presets and templates, switching themes, and enforcing frontmatter-driven metadata to maintain consistency across the component suite.

Can I use shadcn presets to switch themes between different templates?

Yes, you can use shadcn presets to switch themes between different templates, supporting multiple themes and enabling consistent design system alignment across various project templates.

Does the shadcn CLI support component documentation and registry info lookup?

Yes, the shadcn CLI supports component documentation and registry info lookup through dedicated docs and info commands, allowing you to inspect and manage component metadata directly from your project.

Why do I need a components.json file for shadcn/ui?

You need a components.json file for shadcn/ui because it provides centralized project context, enabling consistent imports, path aliasing, and safe defaults when adding or upgrading components from registries.