components-build
Build modern, composable, and accessible React UI components following the components.build specification. Use when creating, reviewing, or refactoring component libraries, design systems, or any reusable UI components. Triggers on tasks involving component APIs, composition patterns, accessibility, styling systems, or TypeScript props.
What this skill does
# Components.build Specification Comprehensive guidelines for building modern, composable, and accessible UI components. Contains 16 rule categories covering everything from core principles to distribution, co-authored by Hayden Bleasel and shadcn. ## When to Apply Reference these guidelines when: - Creating new React components or component libraries - Designing component APIs and prop interfaces - Implementing accessibility features (keyboard, ARIA, focus management) - Building composable component architectures - Styling components with Tailwind CSS and CVA - Publishing components to registries or npm ## Rule Categories by Priority | Priority | Category | Focus | Prefix | |----------|----------|-------|--------| | 1 | Overview | Specification scope and goals | `overview` | | 2 | Principles | Core design philosophy | `principles` | | 3 | Definitions | Common terminology | `definitions` | | 4 | Composition | Breaking down complex components | `composition` | | 5 | Accessibility | Keyboard, screen readers, ARIA | `accessibility` | | 6 | State | Controlled/uncontrolled patterns | `state` | | 7 | Types | TypeScript props and interfaces | `types` | | 8 | Polymorphism | Element switching with `as` prop | `polymorphism` | | 9 | As-Child | Radix Slot composition pattern | `as-child` | | 10 | Data Attributes | `data-state` and `data-slot` | `data-attributes` | | 11 | Styling | Tailwind CSS, cn utility, CVA | `styling` | | 12 | Design Tokens | CSS variables and theming | `design-tokens` | | 13 | Documentation | Component documentation | `documentation` | | 14 | Registry | Component registries | `registry` | | 15 | NPM | Publishing to npm | `npm` | | 16 | Marketplaces | Component marketplaces | `marketplaces` | ## Quick Reference ### 1. Overview - `overview` - Specification scope, goals, and philosophy ### 2. Principles - `principles` - Composability, accessibility, customization, transparency ### 3. Definitions - `definitions` - Common terminology (primitive, compound, headless, etc.) ### 4. Composition - `composition-root` - Root component with Context for shared state - `composition-item` - Item wrapper components - `composition-trigger` - Interactive trigger components - `composition-content` - Content display components - `composition-export` - Namespace export pattern ### 5. Accessibility - `accessibility-semantic-html` - Use appropriate HTML elements - `accessibility-keyboard` - Full keyboard navigation support - `accessibility-aria` - Proper ARIA roles, states, and properties - `accessibility-focus` - Focus management and restoration - `accessibility-live-regions` - Screen reader announcements - `accessibility-contrast` - Color contrast requirements ### 6. State - `state-uncontrolled` - Internal state management - `state-controlled` - External state delegation - `state-controllable` - Support both patterns with useControllableState ### 7. Types - `types-extend-html` - Extend native HTML attributes - `types-export` - Export prop types for consumers - `types-single-element` - One component wraps one element ### 8. Polymorphism - `polymorphism-as-prop` - Change rendered element type - `polymorphism-typescript` - Type-safe polymorphic components - `polymorphism-defaults` - Semantic element defaults ### 9. As-Child - `as-child-slot` - Radix Slot for prop merging - `as-child-composition` - Compose with child components ### 10. Data Attributes - `data-attributes-state` - Use `data-state` for styling states - `data-attributes-slot` - Use `data-slot` for targeting sub-components ### 11. Styling - `styling-cn-utility` - Combine clsx and tailwind-merge - `styling-order` - Base → Variants → Conditionals → User overrides - `styling-cva` - Class Variance Authority for variants - `styling-css-variables` - Dynamic values with CSS variables ### 12. Design Tokens - `design-tokens-css-variables` - Define tokens as CSS variables - `design-tokens-theming` - Support light/dark modes and themes ### 13. Documentation - `documentation-props` - Document all props with JSDoc - `documentation-examples` - Provide usage examples ### 14. Registry - `registry-structure` - Registry file structure - `registry-schema` - Component metadata schema ### 15. NPM - `npm-package-json` - Package configuration - `npm-exports` - Module exports ### 16. Marketplaces - `marketplaces-distribution` - Component distribution strategies ## How to Use Read individual rule files for detailed explanations and code examples: ``` rules/composition/SKILL.md rules/accessibility/SKILL.md rules/styling/SKILL.md ``` Each rule file contains: - Brief explanation of why it matters - Incorrect code example with explanation - Correct code example with explanation - Best practices and common pitfalls ## Full Compiled Document For the complete guide with all rules expanded: `AGENTS.md` ## Key Principles 1. **Composition over Configuration** - Break components into composable sub-components 2. **Accessibility by Default** - Not an afterthought, but a requirement 3. **Single Element Wrapping** - Each component wraps one HTML element 4. **Extend HTML Attributes** - Always extend native element props 5. **Export Types** - Make prop types available to consumers 6. **Support Both State Patterns** - Controlled and uncontrolled 7. **Intelligent Class Merging** - Use `cn()` utility with tailwind-merge ## Authors Co-authored by: - **Hayden Bleasel** ([@haydenbleasel](https://x.com/haydenbleasel)) - **shadcn** ([@shadcn](https://x.com/shadcn)) Adapted as an AI skill by: - **Jordan Gilliam** ([@nolansym](https://x.com/nolansym)) Based on the [components.build](https://components.build) specification.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.