ui-component-builder

Generate React and Tailwind UI components matching DESIGN.md with required states.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill ui-component-builder-cleanexpo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-component-builder
Source: https://github.com/CleanExpo/Pi-Dev-Ops/tree/main/skills/ui-component-builder
Command: npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill ui-component-builder-cleanexpo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of inconsistent, off-brand UI output by generating React/Tailwind components that strictly match the project's DESIGN.md and required interaction/state coverage.

Core Features & Use Cases

  • Design-grounded component generation: Reads DESIGN.md first and applies the project’s typography, spacing, surface, and animation constraints.
  • Variant-first delivery: Produces three variants for the same component, tuned using the dial system (design variance, motion intensity, visual density).
  • Mandatory state completeness: Always includes default, hover, active/selected, loading skeleton, empty state, error, disabled, and visible keyboard focus ring—appropriate for data-fetching and list/collection UI.
  • Output quality guardrails: Enforces rules like no Inter, no hardcoded hex in JSX, no generic gray tokens, grid-based layout patterns, and motion limited to transform/opacity with prefers-reduced-motion handling.
  • Real integration patterns: Supports 21st.dev Magic discovery/generation workflow and includes Pi-CEO dashboard patterns (e.g., session cards, phase indicators, streaming log terminals).

Quick Start

Use the ui-component-builder skill to build a React component from the project’s DESIGN.md by asking it to generate three variants with all interaction states, including a loading skeleton and empty/error/disabled states.

Frequently Asked Questions about ui-component-builder

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

FAQPage Schema
How do I generate React UI components that match my design system tokens exactly?▼

Production-ready React components must include default, hover, active, loading skeleton, empty, error, and disabled states. The builder enforces this mandatory state completeness to ensure accessible interactions and robust data-fetching UI coverage.

Can I build Tailwind UI variants that automatically support reduced-motion accessibility?▼

Yes, you can use Tailwind for dashboard UI development without hardcoded hex values. The builder enforces design token usage and grid-based layout patterns to ensure your admin surfaces remain visually consistent and on-brand.

What's the best way to scaffold multi-variant React components with TypeScript exports?▼

The best way to scaffold multi-variant React components is to generate three tuned variants using a dial system for design variance, motion intensity, and visual density. This produces TypeScript-friendly named exports with correct responsive behavior.

Why do my React UI components have inconsistent styling and missing empty states?▼

React UI components have inconsistent styling and missing empty states when generated without strict design system grounding. Using a DESIGN.md file ensures mandatory state completeness, including loading skeletons and error states, preventing off-brand output.