shadcn

Manage shadcn/ui component installation and styling consistency across monorepo applications.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/dtaborda/startup-saas-template --skill shadcn-dtaborda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/dtaborda/startup-saas-template/tree/main/skills/shadcn
Command: npx skills add https://github.com/dtaborda/startup-saas-template --skill shadcn-dtaborda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill keeps shadcn/ui components consistent by collecting project context, enforcing styling and composition rules, and guiding CLI commands so teams do not ship misaligned layouts or theme variables.

Core Features & Use Cases

  • Documents CLI usage patterns for init, add, search, docs, info, and diff commands with the correct package runner while highlighting registries, preset switching, and recommended workflows.
  • Highlights styling, forms, composition, icons, and base-vs-radix rules so component additions always use semantic tokens, FieldGroup structures, proper groups, and accessible overlays.
  • Provides project-specific context such as aliases, resolved paths, global CSS entry points, monorepo layout, update strategies, registry handling, and complements additional skills for template placement, design direction, and Tailwind practices.

Quick Start

Start by asking for the shadcn info and docs outputs via the correct package runner so you can inspect aliases, Tailwind settings, registries, and installed components before making any changes.

Frequently Asked Questions about shadcn

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

FAQPage Schema
How do I add shadcn/ui components to a monorepo without breaking styling consistency?

To add shadcn/ui components to a monorepo without breaking styling consistency, use CLI commands like init and add while enforcing semantic styling rules and project context metadata. This ensures shared UI resources use proper semantic tokens and FieldGroup structures.

What is the best way to manage shadcn/ui component registries and presets via CLI?

Managing shadcn/ui component registries and presets involves using CLI commands like search, docs, and info with the correct package runner. This approach highlights preset switching and recommended workflows to keep component additions aligned.

How do I resolve Tailwind theme variable misalignment when adding shadcn components?

Resolve Tailwind theme variable misalignment by inspecting aliases, global CSS entry points, and components.json layouts before modifying shared UI resources. Enforcing semantic styling rules and base-vs-radix guidelines ensures accessible overlays and proper groups.

Does shadcn/ui CLI support custom component workflows for monorepo layouts?

shadcn/ui CLI supports custom component workflows for monorepo layouts by utilizing components.json-based configurations and project context metadata. It guides commands like diff and info to manage update strategies and resolved paths across applications.

Why does my shadcn/ui component layout output misaligned styles after an update?

shadcn/ui component layouts output misaligned styles after an update if CLI best practices are ignored. Prevent this by running the info command to verify Tailwind settings and registries, ensuring component additions use semantic tokens.