shadcn

Manage shadcn/ui components and projects using the shadcn CLI with components.json context.

Updated Mar 6, 2026

Search Tags:#ui #documentation #components #cli #registry #shadcn #preset

Ready to run

npx skills add https://github.com/jcteague/wheelbase --skill shadcn-jcteague

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/jcteague/wheelbase/tree/main/.claude/commands/.agents/skills/shadcn
Command: npx skills add https://github.com/jcteague/wheelbase --skill shadcn-jcteague

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The shadcn Skill unit provides a centralized, non-intrusive way to manage shadcn/ui components and project workflows, including adding, searching, fixing, debugging, styling, and composing UI within a repository that uses a components.json registry.

Core Features & Use Cases

Manages shadcn/ui components and projects across multiple apps using a single workflow.
Provides project context, component docs, and usage examples to accelerate UI development.
Triggers for shadcn init, creating an app with --preset, or switching presets to streamline setup and updates.

Quick Start

Run the shadcn commands to initialize and manage your shadcn/ui components in your project.

Frequently Asked Questions about shadcn

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

FAQPage Schema

How do I add and manage shadcn/ui components in an existing project?▼

To manage shadcn/ui components, you use the shadcn CLI within a project configured with a components.json file. This allows you to add, search, fix, and style UI components directly across your repository's registries.

Can I initialize a new app using a shadcn preset?▼

Yes, you can initialize a new app using a shadcn preset by running the shadcn init command with the --preset flag. This streamlines setup and allows you to switch presets during the project lifecycle.

What is the best way to generate documentation for shadcn/ui components?▼

Generating component docs and usage examples for shadcn/ui is handled by applying the shadcn CLI workflow. It uses your components.json context to provide project-specific documentation and accelerate UI development.

Does this workflow support managing shadcn/ui components across multiple apps?▼

Yes, this workflow supports managing shadcn/ui components across multiple apps using a single centralized process. It operates non-intrusively within repositories that use a components.json registry.

Why do I need a components.json file to use shadcn CLI workflows?▼

A components.json file is required because it provides the registry context needed for the shadcn CLI to properly add, search, debug, and style UI components within your specific project configuration.