Build UI components with shadcn/ui. Pairs with the Stitch design loop to ship structured, accessible components quickly.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add nexu-io/open-design --skill shadcn-ui --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Shadcn Ui?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nexu-io-shadcn-ui)More formats (shields.io, HTML) on the badges page.
---
name: shadcn-ui
description: |
Build UI components with shadcn/ui. Pairs with the Stitch design loop to ship structured, accessible components quickly.
triggers:
- "shadcn"
- "shadcn ui"
- "shadcn components"
- "accessible components"
od:
mode: design-system
category: design-systems
upstream: "https://github.com/google-labs-code/skills"
---
# shadcn-ui
> Curated from Google Labs (Stitch).
## What it does
Build UI components with shadcn/ui. Pairs with the Stitch design loop to ship structured, accessible components quickly.
## Source
- Upstream: https://github.com/google-labs-code/skills
- Category: `design-systems`
## How to use
This catalogue entry advertises the skill in OpenDesign so the agent
discovers it during planning. To run the full upstream workflow with
its original assets, scripts, and references, install the upstream
bundle into your active agent's skills directory:
```bash
# Inspect the upstream README for exact paths
open https://github.com/google-labs-code/skills
```
Then ask the agent to invoke this skill by name (`shadcn-ui`) or with
one of the trigger phrases listed in this skill's frontmatter.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
