shadcn

Organize shadcn/ui component integration across projects with CLI workflows.

3|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ricardocamisa/vbacode --skill shadcn-ricardocamisa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/ricardocamisa/vbacode/tree/main/.crush/skills/shadcn
Command: npx skills add https://github.com/ricardocamisa/vbacode --skill shadcn-ricardocamisa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating and standardizing the use of shadcn/ui components across multiple projects to ensure consistency, faster onboarding, and reduced friction when wiring UI primitives.

Core Features & Use Cases

  • Centralizes project context awareness for shadcn/ui components, documentation, and usage examples.
  • Facilitates adding, searching, fixing, debugging, styling, and composing UI components with a CLI-driven workflow.
  • Triggers for common project actions like shadcn init, --preset switching, and app creation with presets.

Quick Start

Install the CLI, initialize a project with a preset, and start adding components to your shadcn/ui setup.

Frequently Asked Questions about shadcn

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

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

To standardize shadcn/ui components across multiple projects, use a CLI-driven workflow to centralize project context, ensuring UI consistency and reducing onboarding friction when wiring primitives.

What is the best way to manage shadcn/ui project initialization and preset switching?

The best way to manage shadcn/ui initialization and preset switching is through CLI triggers that apply project context awareness. This facilitates app creation with presets and standardizes the setup workflow for UI components.

Can I use the CLI to add and debug shadcn/ui components directly?

Yes, you can use the CLI to add, search, fix, debug, and compose shadcn/ui components directly. It centralizes documentation and usage examples to streamline the styling and UI customization workflow.

Does this approach help with wiring UI primitives for faster project onboarding?

Yes, organizing component integration across projects ensures reduced friction and consistent styling when wiring UI primitives, directly leading to faster project onboarding.

What are the limitations of managing shadcn/ui components via a CLI workflow?

This CLI workflow focuses strictly on project setup, component creation, styling, and preset switching. Complex custom logic outside standard UI composition and preset boundaries requires manual intervention beyond the CLI's operational scope.