component-patterns

Standardize reusable UI component patterns across Figurio surfaces.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/cellarwood/figurio --skill component-patterns-cellarwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-patterns
Source: https://github.com/cellarwood/figurio/tree/main/skills/component-patterns
Command: npx skills add https://github.com/cellarwood/figurio --skill component-patterns-cellarwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and engineers need a shared set of reusable UI primitives and patterns to accelerate development and ensure consistency across storefront, checkout, preview, order, and admin interfaces.

Core Features & Use Cases

  • Explicit prop contracts and small, stable APIs for components.
  • Variant-driven design enabling predictable composition and accessibility.
  • Pattern library for building and reviewing UI primitives across surfaces.

Quick Start

Import and start using the shared component patterns library in your project.

Frequently Asked Questions about component-patterns

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

FAQPage Schema
How do I standardize reusable React component patterns to reduce duplication across UI surfaces?

Standardize reusable React component patterns by applying explicit prop contracts, small stable APIs, and variant-driven composition. This ensures predictable UI behavior and reduces code duplication across storefront, checkout, and admin surfaces.

What are explicit prop contracts for UI primitives and when do I need them?

Explicit prop contracts for UI primitives are strict, documented API boundaries for component inputs. You need them when building shared UI libraries to ensure components remain stable, predictable, and easy to compose across different application surfaces.

How do I build accessible React components using Radix primitives and Tailwind CSS?

Build accessible React components by leveraging Radix primitives for behavior and Tailwind CSS for styling. This approach combines accessible foundation logic with variant-driven styling to create predictable, compliant UI patterns.

Does this component pattern library work with TypeScript and shadcn-ui for storefront and admin surfaces?

Yes, the component pattern library works with TypeScript and shadcn-ui. It standardizes UI primitives using Radix foundations, making them applicable for building and reviewing components across storefront, checkout, preview, order, and admin surfaces.

What is variant-driven composition for UI components and why does it matter?

Variant-driven composition is a design approach that builds component variations from small, stable APIs rather than monolithic components. It matters because it enforces predictable styling and accessibility considerations while preventing API bloat in shared UI libraries.

Why does UI consistency break down across checkout and admin surfaces without shared component patterns?

UI consistency breaks down across surfaces when shared primitives lack explicit prop contracts and variant-driven design. Standardizing these reusable UI component patterns ensures accessibility and stable APIs are applied uniformly across all Figurio interfaces.