building-components

Create modular React UI components using a Root/Item/Trigger/Content architecture.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/TheSethRose/PeptideCalc --skill building-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-components
Source: https://github.com/TheSethRose/PeptideCalc/tree/main/.github/skills/building-components
Command: npx skills add https://github.com/TheSethRose/PeptideCalc --skill building-components

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Building Components skill guides engineers to create modern, accessible, and composable UI components by decomposing complex interfaces into reusable primitives and patterns, enabling scalable design systems across projects.

Core Features & Use Cases

  • Composable architecture: promotes a Root/Item/Trigger/Content pattern to enable reusable UI blocks and clean separation of concerns.
  • Accessibility-by-default: emphasizes ARIA semantics, keyboard navigation, and focus management as core design requirements.
  • Design tokens and theming: aligns component primitives with design tokens for consistent theming and branding.
  • Pattern references & guidance: provides documented patterns like asChild, data-slot, polymorphism, and type-safe compositions to speed up development.
  • DX-focused documentation: includes extensive references and examples to improve developer experience and onboarding.

Quick Start

Provide a plan to scaffold a new composable UI library by implementing Root, Item, Trigger, and Content following the references.

Frequently Asked Questions about building-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build accessible UI components in React that scale across design systems?

Build accessible UI components in React by decomposing interfaces into composable Root, Item, Trigger, and Content primitives. This architecture enforces ARIA semantics, keyboard navigation, and focus management by default, enabling scalable design systems with consistent theming across applications.

What is the composable Root/Item/Trigger/Content pattern for React components?

The composable Root/Item/Trigger/Content pattern is a modular architecture that decomposes complex UI interfaces into reusable primitives. It separates structural concerns, allowing developers to assemble accessible React components with clean boundaries and predictable behavior.

How do I scaffold a new composable UI library from scratch?

Scaffold a composable UI library by implementing Root, Item, Trigger, and Content primitives following documented pattern references. Align these components with design tokens for consistent theming, and use type-safe compositions to ensure scalable, accessible React component blocks.

Can I use design tokens for consistent theming across React component primitives?

Yes, you can use design tokens for consistent theming across React component primitives. The composable architecture aligns component primitives with design tokens, ensuring consistent branding and theming across scalable design systems within your applications.

What's the best way to implement polymorphism and type-safe compositions in React UI components?

The best way to implement polymorphism and type-safe compositions is by applying documented patterns like asChild and data-slot within a composable Root/Item/Trigger/Content architecture. These patterns enable flexible, reusable UI blocks while maintaining accessibility and type safety.

Why does my React UI component library lack consistent accessibility and focus management?

Your React UI component library lacks consistent accessibility because it does not enforce ARIA semantics, keyboard navigation, and focus management as core design requirements. Adopting a composable architecture with accessibility-by-default ensures these standards are met across all primitives.