shadcn/ui Best Practices

Use this skill for shadcn/ui authoring, review, architecture decisions, UI cleanup, and modernization. Center the answer on the fact that shadcn/ui ships source code you own: prefer composition, semantic tokens, and maintainable project conventions over one-off styling hacks.

Use This Skill When

• Building or reviewing shadcn/ui interfaces, pages, forms, overlays, or feature UIs
• Deciding between existing shadcn primitives and custom markup
• Setting up or auditing components.json, aliases, Tailwind v4 wiring, or theme tokens
• Debugging broken composition, invalid states, trigger APIs, or over-customized styling
• Modernizing older shadcn patterns such as deprecated toast usage or brittle color overrides
• Organizing feature code around components/ui, app-level feature components, and local state boundaries

Out Of Scope

• Registry publishing or MCP workflows unless the user's main problem is specifically about registry authoring
• Framework-specific deployment or routing details that are not materially affecting shadcn usage
• Replacing shadcn/ui with a different component system