shadcn

Manage shadcn/ui component lifecycle and styling in Next.js or Vite monorepos.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/sansalgo/c4t --skill shadcn-sansalgo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/sansalgo/c4t/tree/main/.agents/skills/shadcn
Command: npx skills add https://github.com/sansalgo/c4t --skill shadcn-sansalgo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of managing a shadcn/ui component library, ensuring consistent styling, correct component composition, and adherence to accessibility standards across your project.

Core Features & Use Cases

  • Component Lifecycle Management: Automates adding, updating, and debugging components while preserving local changes via smart diffing.
  • Styling & Composition Enforcement: Enforces semantic color tokens, proper layout patterns, and correct component hierarchies to prevent "div soup" and maintain design system integrity.
  • Use Case: When building a complex dashboard, use this skill to ensure your forms use the correct FieldGroup/Field structure, your buttons use data-icon attributes, and your overlays are accessible, all while keeping your Tailwind configuration clean.

Quick Start

Use the shadcn skill to add the button and card components to the current project and verify they follow the project's styling rules.

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 in a Next.js or Vite monorepo?

You can manage shadcn/ui components in a Next.js or Vite monorepo by using the shadcn CLI to resolve component paths, automate updates, and preserve local changes via smart diffing.

How do I update shadcn/ui components without losing my local styling changes?

Updating shadcn/ui components without losing local changes is handled through smart diffing, which automates component updates while preserving your custom styling and layout modifications.

Does this approach work with both Tailwind and Vite environments?

Yes, this approach works with both Vite and Next.js monorepos, resolving component paths and Tailwind versions to ensure correct UI primitive configuration and styling.

How do I enforce semantic design tokens and prevent div soup in my UI?

To enforce semantic design tokens and prevent div soup, the system validates correct component hierarchies, proper layout patterns, and data-icon attributes to maintain design system integrity.

Do I need the shadcn CLI to add and audit UI primitives?

Yes, you need the shadcn CLI along with project-specific configuration to add, update, and audit UI primitives while resolving icon libraries and Tailwind versions.

Why do my shadcn/ui overlays fail accessibility requirements?

shadcn/ui overlays fail accessibility requirements when component composition lacks proper hierarchies, which this system resolves by enforcing semantic color tokens and accessible layout structures.