shadcn

Organize shadcn/ui components and projects using components.json configuration.

1|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/kubermatic/kubelb-dashboard --skill shadcn-kubermatic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/kubermatic/kubelb-dashboard/tree/main/.agents/skills/shadcn
Command: npx skills add https://github.com/kubermatic/kubelb-dashboard --skill shadcn-kubermatic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages and standardizes the use of shadcn/ui across projects, providing centralized context, docs, and usage examples to accelerate UI development.

Core Features & Use Cases

  • Centralized project context for shadcn/ui integration, including docs and examples.
  • Trigger-based workflows for initialization and preset switching across registries.
  • Guidance and enforcement of best practices for component composition, forms, and styling.

Quick Start

In your project, run the shadcn workflow to auto-configure UI components, registries, and presets.

Frequently Asked Questions about shadcn

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

FAQPage Schema
How do I initialize shadcn/ui components and presets in an existing project?

To initialize shadcn/ui, run the shadcn init workflow to auto-configure UI components, registries, and presets within your workspace.

What is the purpose of a components.json file in shadcn/ui?

The components.json file provides centralized project context for shadcn/ui, enabling activation triggers for component integration and preset switching across registries.

Can I switch shadcn/ui presets across different component registries?

Yes, you can switch shadcn/ui presets across registries using trigger-based workflows that apply preset changes and reconfigure your project components.

How do I standardize shadcn/ui component composition and styling across multiple projects?

You standardize shadcn/ui across projects by using centralized context, docs, and trigger-based workflows that enforce best practices for component composition and styling.

Does this approach work with existing component registries and custom presets?

Yes, it organizes and provisions shadcn/ui components by applying across projects that use existing component registries, custom presets, and a components.json file.