shadcn

Manage shadcn/ui components and presets across projects with components.json.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Yahia89/ordering-food --skill shadcn-yahia89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/Yahia89/ordering-food/tree/main/.agents/skills/shadcn
Command: npx skills add https://github.com/Yahia89/ordering-food --skill shadcn-yahia89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes the management and activation of shadcn/ui components and presets across projects, reducing setup time and ensuring consistent UI libraries.

Core Features & Use Cases

  • Automates project context loading and component guidance for shadcn/ui.
  • Guides initialization, preset switching, and registry interactions across registries and component.json configurations.
  • Provides structured, rules-based guidance for design-system adoption and component governance.

Quick Start

Initialize shadcn in your project and begin managing components with the built-in CLI guidance.

Frequently Asked Questions about shadcn

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

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

To configure shadcn/ui components across projects, you can use a centralized skill definition that loads project context and manages components.json files to ensure consistent UI library setups. This reduces manual setup time and standardizes design-system adoption.

What is the best way to switch shadcn/ui presets in an existing project?

The best way to switch shadcn/ui presets is by activating guided registry interactions that read your existing components.json file. This workflow allows you to swap configurations and initiate new app presets without breaking current UI dependencies.

Can I use shadcn/ui with a custom registry setup?

Yes, you can use shadcn/ui with custom registries. The workflow supports registry interactions across various configurations, allowing you to pull components from custom sources while maintaining structured, rules-based governance for your frontend design system.

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

Yes, a components.json file is required to manage shadcn/ui workflows effectively. The skill detects this file to load operational instructions, apply safety standards, and provide accurate component guidance for your specific frontend environment.

Why does my shadcn/ui initialization fail when applying a new preset?

shadcn/ui initialization may fail if the project context is missing required configurations or the components.json file is misconfigured. Ensure your SKILL.md frontmatter includes the correct name and description to properly load operational instructions.

How does the shadcn skill handle component governance for frontend design systems?

The shadcn skill handles component governance by providing structured, rules-based guidance for design-system adoption. It centralizes management of UI components and presets, ensuring consistent libraries and enforcing documentation standards across projects.