shadcn

Manage shadcn/ui component lifecycle with registry imports and Tailwind styling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building and maintaining shadcn/ui components often leads to inconsistent styling, incorrect composition, accessibility gaps, and API misuse when working across different presets (base vs radix) or integrating third-party registry components. This Skill eliminates those issues by enforcing project-aligned best practices and automating common CLI workflows.

Core Features & Use Cases

  • Component Lifecycle Management: Add, search, update, and debug shadcn/ui components from official and community registries, with automatic import path correction for third-party components to match your project's aliases.
  • Best Practice Enforcement: Enforces strict composition rules, semantic Tailwind styling, accessibility requirements, and correct base/radix API usage to prevent common UI bugs and maintain consistency.
  • Use Case: When building a Next.js settings page, use this Skill to add pre-built Form, ToggleGroup, and Dialog components that match your project's preset, icon library, and Tailwind configuration, with no manual styling or import fixes required.

Quick Start

Use the shadcn skill to add a pre-built, correctly configured Button component to your existing shadcn/ui project that matches your project's preset and icon library.

Frequently Asked Questions about shadcn

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

FAQPage Schema
How do I fix inconsistent styling and API misuse when adding shadcn/ui components to my React project?

Fix inconsistent shadcn/ui component styling and API misuse by enforcing strict composition rules, semantic Tailwind styling, and correct base/radix API usage. This ensures components align with your project's preset, icon library, and configuration, preventing common UI bugs and manual styling errors.

How do I add pre-built shadcn/ui components from a community registry without breaking import paths?

Add pre-built shadcn/ui components from community registries with automatic import path correction. This process matches third-party components to your project's specific path aliases, ensuring seamless integration without requiring manual import fixes or configuration adjustments.

Does this approach work with existing Next.js and Tailwind configurations?

Yes, this approach works with existing Next.js and Tailwind configurations. It automatically aligns component additions with your project-specific setup, including path aliases, icon libraries, and Tailwind versions, ensuring pre-built components match your environment perfectly.

What is the best way to manage the shadcn/ui component lifecycle across different presets?

The best way to manage the shadcn/ui component lifecycle across base and radix presets is by automating CLI workflows. This allows you to add, search, update, and debug components while enforcing accessibility standards and semantic Tailwind styling across different presets.

Why do my shadcn/ui components have accessibility gaps and incorrect composition?

Your shadcn/ui components have accessibility gaps and incorrect composition due to inconsistent manual styling and API misuse. Enforcing project-aligned best practices, semantic Tailwind styling, and strict accessibility requirements eliminates these issues and maintains UI consistency across your React project.