domains / families / design / shadcn

shadcn

combined

Shadcn/ui-inspired design with minimal, clean components, monochrome palette, and utility-first patterns. Manages shadcn/ui components and projects, providing context, documentation, and usage patterns for building modern design systems.

When to use

• Use when adding new components from shadcn/ui or community registries.
• Use when styling, composing, or debugging existing shadcn/ui components.
• Use when initializing a new project or switching design system presets.
• Use to retrieve component documentation, examples, and API references.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies address different layers of the same skill. The bergside copy is a design-system authoring guide: it defines visual foundations (typography, color tokens, spacing), accessibility tone, and a workflow for writing design-system documentation. The sickn33 copy is an implementation/CLI guide: it covers the shadcn CLI, project context, component composition rules, Tailwind styling constraints, form patterns, and icon usage. Neither copy contains the other's material steps, and crowning one would hide a real alternative. They overlap only in the general goal of producing consistent shadcn/ui output.