building-components
Skill32 starsChanged 6 months agoMITView on GitHub
Vercel's guide for building modern, accessible, and composable UI components: accessibility, composable APIs, design tokens, publishing to npm or a registry, and writing component docs. From the components.build project.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- Kemdirimakujuobi/skillstheir own version, first seen Nov 1, 2026
- ManatoYamashita/skillstheir own version, first seen Nov 1, 2026
- trancethehuman/template-next-agenttheir own version, first seen Oct 13, 2026
- Compound-inc/rifttheir own version, first seen Oct 8, 2026
- tazo90/next-openapi-gentheir own version, first seen Oct 8, 2026
- JMBeresford/retromtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use vercel-cli, vercel-composition-patterns and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DatabricksSkillvercel-cli
Deploy, manage, and develop projects on Vercel from the command line
Also in 3 projects that use this
SentrySkillvercel-composition-patterns
Also in 7 projects that use this
VercelSkillai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
Also in 3 projects that use this
VercelSkillai-sdk
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Also in 3 projects that use this
VercelSkillvercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Also in 7 projects that use this
VercelSkillweb-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Also in 5 projects that use this
- +1 more from vercel-labs
- +1 more from vercel
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- kokonut-labs/kokonutui★ 2.3ksame name
- JMBeresford/retrom★ 2.1ksame name
- vercel/components.build★ 793same name
- tazo90/next-openapi-gen★ 196same name
- Compound-inc/rift★ 124same name
- databricks/devhub★ 29same name
- Kemdirimakujuobi/skills★ 9same name
- trancethehuman/template-next-agent★ 3same name
- FelipeAngeli/skills★ 2same name
- caprica-Six/hyperliquid-insights-web★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository170 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-agentsSkill
- accessibility-catalogueSkill
- addyosmani-qualitySkill
- ai-graphic-design-skillSkill
- algorithmic-artSkill
- anatomySkill
- animate-css-skillSkill
- animate-skillSkill
- anthropics-skillsSkill
- antvis-chart-skillsSkill
- apple-hig-skillsSkill
- assimovt-productskillsSkill
- awesome-design-skillsSkill
- baseline-uiSkill
- bencium-ux-designerSkill
- brand-design-mdSkill
- callstack-agent-skillsSkill
- cc-slidevSkill
- chadboyda-gtmSkill
- claud3Skill
- claude2figmaSkill
- claudedesignskillsSkill
- claude-pm-skillsSkill
- claude-wireframe-skillSkill
- cloudai-threejsSkill
- cloudflare-web-perfSkill
- color-expertSkill
- composio-artifactsSkill
- content-catalogueSkill
- content-strategySkill
- copywriting-skillSkill
- coreyhaines-marketingSkill
- creative-directorSkill
- css-animation-skillSkill
- d3js-skillSkill
- dark-pattern-auditSkill
- data-analysis-skillSkill
- data-viz-agentSkill
- deanpeters-pm-skillsSkill
- design-auditorSkill
- design-briefSkill
- design-catalogueSkill
- design-consultationSkill
- design-debt-auditSkill
- design-engineering-catalogueSkill
- designer-skillsSkill
- design-for-aiSkill
- design-htmlSkill
- design-impact-reportingSkill
- design-labSkill
- design-motion-principlesSkill
- design-negotiationSkill
- design-review-garrytanSkill
- design-sprintSkill
- design-system-governanceSkill
- design-tokens-skillSkill
- design-with-claudeSkill
- digidai-pmSkill
- dimensional-drawingSkill
- The first 60 shown.
The file
Files
building-components
Catalogue stub — full skill: vercel/components.build (
skills/building-components)
<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->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:
[ -e ~/.agents/skills/building-components ] && echo "global" || echo "project"Global:
npx skills add vercel/components.build --skill building-components -g -yProject:
npx 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)
<!-- das:install:end -->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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

