shadcn-ui · podo — Claude Code skill: what it does, how to install
Guides AI coding agents through searching, adding, and composing shadcn/ui components accurately.
MIT 271 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill shadcn-ui -a claude-codeWhat shadcn-ui does
This skill establishes a structured shadcn/ui workflow tailored to your project. The assistant inspects project settings by executing npx shadcn@latest info --json, queries official and community registries, and installs items using proper CLI arguments. Instead of introducing arbitrary CSS classes, it relies on existing variants and design tokens.
Node.js is strictly required because the workflow invokes shadcn via your local package runner. You also need a components.json configuration file present in the project root, or you must initialize one via shadcn init.
A known naming overlap exists: google-stitch-skills provides a pointer using the same shadcn-ui name, meaning installing both overwrites the previous setup.
What it helps with
- add missing shadcn components via CLI without manual copy-paste
- compose complex layouts like settings views from Cards and Tabs
- resolve styling mismatches by using semantic theme variables
- integrate custom presets and external component registries
Example prompts for the agent
- Add a shadcn component for user avatar dropdown
- Check our components.json and build a checkout form with shadcn/ui
- Fix invalid variant styles in this ui component
How to install shadcn-ui
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill shadcn-ui -a claude-code2Manually: put the files in place
~/.claude/skills/shadcn-ui/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/shadcn-ui/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill shadcn-ui -a codex2Manually: put the files in place
.agents/skills/shadcn-ui/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill shadcn-ui -a cursor2Manually: put the files in place
.cursor/skills/shadcn-ui/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/shadcn-ui2Manually: put the files in place
.github/skills/shadcn-ui/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill shadcn-ui -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/shadcn-uiManually: put the files in place
.devin/skills/shadcn-ui/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill shadcn-ui -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about shadcn-ui
How to install shadcn-ui in Claude Code?
Run npx skills add podo/design-agent-skills --skill shadcn-ui -a claude-code in your terminal. It puts the skill configuration into ~/.claude/skills/shadcn-ui/SKILL.md.
What does shadcn-ui do?
It orchestrates shadcn/ui component discovery, installation, and composition while checking local configurations to avoid common styling mistakes.
What are the runtime requirements?
You need Node.js installed to execute npx shadcn commands, roughly 71 MB of disk space, and a project initialized with components.json.
Source text
SKILL.md · MIT
--- name: shadcn-ui description: | Project-aware shadcn/ui workflow for searching, adding, composing, and fixing components with correct patterns. Reads the local project's shadcn config and installed components and avoids common shadcn anti-patterns during implementation. triggers: - "shadcn" - "shadcn/ui" - "shadcn component" - "ui component" das: category: visual-components upstream: "https://github.com/shadcn-ui/ui" upstream_path: "skills/shadcn/SKILL.md" version: latest install: true --- # shadcn-ui > Catalogue stub — full skill: [shadcn-ui/ui](https://github.com/shadcn-ui/ui) (`skills/shadcn`) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** Upstream names this skill `shadcn`, so it installs next to this pointer (the pointer is not replaced). - Global: `f=~/.agents/skills/shadcn/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/shadcn/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `shadcn`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/shadcn-ui ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add shadcn-ui/ui --skill shadcn -g -y ``` **Project:** ```bash npx skills add shadcn-ui/ui --skill shadcn -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Heads-up** - **Requires:** Node.js: the skill runs the shadcn CLI through your package runner (`npx shadcn@latest ...`, fetched from npm at use time), including `info --json` for project context; A project with a components.json file (or one you are about to create with `shadcn init`) - **License:** MIT - **Download size:** ~71 MB. - **Name collision:** `shadcn-ui` is also written by `google-stitch-skills` (its install or its catalogue pointer); installing both overwrites the earlier one. <!-- das:install:end --> ## Invoke after install - Skill name: `shadcn` - Trigger phrases: "shadcn", "shadcn/ui", "shadcn component", "ui component" ## What it does Provides a project-aware workflow for working with shadcn/ui: searching the available component registries (including community registries), adding components with the correct CLI command, composing components from existing ones (a settings page is Tabs + Card + form controls), using built-in variants and semantic colors before custom styles, and fixing common implementation mistakes. It also covers presets, registries and design-system pages. The skill loads project context by running `npx shadcn@latest info --json`. The same upstream repository ships a separate `migrate-radix-to-base` skill for moving components from Radix UI to Base UI; it is not part of this stub (add it with `npx skills add shadcn-ui/ui --skill migrate-radix-to-base`). ## When NOT to use - A non-shadcn component library, or a design system built from scratch — use `design-consultation` - Google Stitch to shadcn conversion — use `google-stitch-skills`
© podo · MIT · podo/design-agent-skills
Similar skills
All skills for Frontend and UI →shadcn-ui by other authors comes first.