building-components
Catalogue stub — full skill: vercel/components.build (
skills/building-components)
Decision tree
-
Is the full skill already installed?
- Global:
f=~/.agents/skills/building-components/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" - Project:
f=.agents/skills/building-components/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" installed→ the skill is installed asbuilding-components, invoke it and proceedpointer→ go to step 2
- Global:
-
Detect scope, then install:
bash[ -e ~/.agents/skills/building-components ] && echo "global" || echo "project"Global:
bashnpx skills add vercel/components.build --skill building-components -g -yProject:
bashnpx skills add vercel/components.build --skill building-components -yClaude Code: send a command as a chat message starting with
!to run it without leaving the conversation.
Heads-up
- License: Apache-2.0 (LICENSE notice; GitHub reports NOASSERTION)
Invoke after install
- Skill name:
building-components - Trigger phrases: "building components", "build accessible components", "composable component API", "components.build"
What it does
Guides building modern UI components that are accessible, composable, and themeable: designing composable APIs, implementing accessibility, setting up design tokens, publishing components to npm or a registry, and writing component documentation. Distilled from the components.build handbook.
When NOT to use
- A project-aware shadcn/ui workflow (adding and composing registry components) → use
shadcn-ui - React/Next.js performance or composition patterns → use
vercel-skills - Visual design direction rather than component architecture → use
hallmarkortaste-skill


