shadcn

Detect valid Skill units and generate structured metadata from SKILL.md frontmatter.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/JoshCantCode/Stack --skill shadcn-joshcantcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadcn
Source: https://github.com/JoshCantCode/Stack/tree/main/.opencode/skills/shadcn
Command: npx skills add https://github.com/JoshCantCode/Stack --skill shadcn-joshcantcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates discovery and documentation of shadcn/ui components, enabling automated tooling to identify valid Skill units and generate consistent metadata for project setup and governance.

Core Features & Use Cases

  • Detects Skill units by the mandatory SKILL.md presence at root and asserts required frontmatter fields (name, description) for discovery.
  • Produces structured metadata including name, tagline, description, request, complexity, category, keywords, dependencies, and components.
  • Performs safety and conformance checks, including toxicity assessment and validation of optional resources (scripts/, references/, assets/).

Quick Start

Run the shadcn CLI in your project to initialize or update your UI components.

Frequently Asked Questions about shadcn

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

FAQPage Schema
How do I validate frontmatter metadata for shadcn/ui components?

To extract metadata, the system reads the mandatory SKILL.md frontmatter at the project root. It automatically pulls structured fields including name, tagline, description, request, complexity, category, and keywords for discovery.

What is the best way to detect valid skill units in a UI component project?

Valid skill units are detected by asserting the mandatory presence of a SKILL.md file at the root directory. This mechanism enables automated tooling to identify valid components and generate consistent project metadata.

Does shadcn/ui component validation include safety and toxicity checks?

Yes, component validation includes safety and conformance checks. The workflow performs toxicity assessments and validates optional resources such as scripts, references, and assets directories during metadata generation.

What metadata fields are required to generate structured documentation for skill discovery?

Structured documentation requires name and description fields at minimum. The system also extracts tagline, request, complexity, category, keywords, dependencies, and components to produce comprehensive metadata for project governance.

Can I validate optional resources like scripts and assets alongside UI components?

Yes, you can validate optional resources alongside components. The workflow performs conformance checks on optional directories including scripts, references, and assets to ensure complete project setup and governance.

Why does my skill unit fail discovery checks during shadcn/ui project setup?

Skill unit discovery fails when the mandatory SKILL.md file is missing from the root directory. The system enforces strict frontmatter validation, requiring essential fields like name and description to pass conformance checks.