shadcn

Manage shadcn/ui components, presets, and project context via CLI workflows.

Updated Aug 23, 2026

Search Tags:#ui #components #cli #registry #shadcn #presets

Ready to run

npx skills add https://github.com/znarfm/vet --skill shadcn-znarfm

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Core Features & Use Cases

Centralizes management of shadcn/ui components across projects
Provides project context, component docs, and usage examples from registries
Streamlines init/add/docs workflows and preset switching for consistent UI tooling

Quick Start

Initialize a project with a shadcn preset and manage components using 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 and manage shadcn/ui components in an existing project?▼

To manage shadcn/ui components, use the CLI to initialize projects, add components, resolve documentation, and switch presets. This provides project context and usage examples directly from component registries for consistent UI tooling.

What is the best way to switch shadcn/ui presets during project initialization?▼

Switching shadcn/ui presets is handled by applying a --preset code during project creation or using CLI commands. This streamlines workflow transitions and ensures consistent component usage across teams working within the same components.json configuration.

Does this work with projects that only use a custom component registry?▼

Yes, it applies to any project utilizing component registries, presets, or a components.json file. It centralizes management by resolving documentation and providing usage examples from those registries for your custom UI components.

When do I need to use a components.json file for shadcn/ui?▼

A components.json file is needed when managing shadcn/ui components, applying presets, or resolving documentation. It provides the necessary project context for the CLI to accurately add, search, and style UI components across your codebase.

Why are my shadcn CLI commands not resolving component documentation correctly?▼

Documentation resolution issues often stem from missing project context or an invalid components.json setup. The CLI relies on this configuration to fetch accurate component docs and usage examples from the specified registries.

Can I debug and style shadcn/ui components using the command line?▼

Yes, you can debug, fix, and style shadcn/ui components using the CLI. It centralizes these tasks by leveraging project context and registry documentation to ensure consistent component composition and styling.