vercel-composition-patterns

Refactor React component libraries using composition patterns to reduce boolean props.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/rondevz/phant --skill vercel-composition-patterns-rondevz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-composition-patterns
Source: https://github.com/rondevz/phant/tree/main/.agents/skills/vercel-composition-patterns
Command: npx skills add https://github.com/rondevz/phant --skill vercel-composition-patterns-rondevz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex React component libraries often explode in booleans and prop-driven variants. This Skill promotes using composition patterns to craft flexible, maintainable UI primitives and reduce boolean prop proliferation.

Core Features & Use Cases

  • Flexible component composition through compound components and shared context.
  • State is lifted and injected via providers to enable UI reuse across apps.
  • Clear variants and explicit component architecture to improve readability and maintainability.

Quick Start

Provide a minimal example converting a boolean-driven component into explicit variant components.

Frequently Asked Questions about vercel-composition-patterns

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

FAQPage Schema
How do I reduce boolean prop proliferation in React components?

To reduce boolean prop proliferation in React components, apply composition patterns by enforcing explicit variants and using context-based state management to build flexible, maintainable UI primitives.

What is the best way to manage shared state in compound React components?

Managing shared state in compound React components is best achieved by lifting state and injecting it via providers, enabling flexible composition and UI reuse across different applications.

How do I refactor a React component library for scalable UI architecture?

Refactor a React component library for scalable UI architecture by replacing boolean-driven variants with explicit component compositions and shared context, ensuring stable APIs across multiple teams.

Does this React composition approach work with React 19 API guidelines?

Yes, this composition approach works with React 19 API guidelines, enforcing explicit variants, context-based state management, and stable component APIs to ensure safe composition.

When should I use explicit variants over boolean props in React?

Use explicit variants over boolean props in React when designing reusable UI primitives for large libraries, as explicit architecture improves readability, maintainability, and prevents component API explosion.