vercel-composition-patterns

Refactor React components with boolean props into compound composition patterns.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Omar-Cc/Integrador-II --skill vercel-composition-patterns-omar-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-composition-patterns
Source: https://github.com/Omar-Cc/Integrador-II/tree/main/frontend/.agents/skills/composition-patterns
Command: npx skills add https://github.com/Omar-Cc/Integrador-II --skill vercel-composition-patterns-omar-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid complex React components caused by excessive boolean props, tangled state logic, and inflexible APIs by applying scalable composition patterns.

Core Features & Use Cases

  • Compound Components: Design reusable component APIs with shared context and flexible composition instead of prop-heavy configurations.
  • State Architecture Patterns: Separate UI from state management, define dependency-injectable context interfaces, and lift state into providers.
  • React Component Design: Create explicit variants, prefer children-based composition, and apply React 19 patterns for modern component implementations.

Quick Start

Ask the skill to refactor a React component with too many boolean props into a composable compound component architecture.

Frequently Asked Questions about vercel-composition-patterns

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

FAQPage Schema
How do I refactor React components with too many boolean props?

Reduce React component complexity by applying scalable composition patterns, replacing boolean prop proliferation with compound components, context providers, and explicit variants.

What is the compound components pattern in React?

The compound components pattern designs reusable React APIs using shared context and flexible children-based composition instead of prop-heavy configurations.

How do I separate UI state from components using context providers?

Separate UI from state management by defining dependency-injectable context interfaces and lifting state architecture into context providers.

Does this React component architecture approach work with React 19?

Yes, this approach applies React 19 implementation patterns for modern component design, including explicit variants and children-based composition.

What's the best way to design a reusable React component library API?

Design reusable React component library APIs using compound components with shared context, explicit variants, and dependency injection to avoid inflexible configurations.

When should I avoid using boolean props in React components?

Avoid boolean props in React components when they cause tangled state logic and inflexible APIs, switching to explicit variants and scalable composition patterns instead.