react-composition-patterns

Replace boolean props with explicit composition patterns in React components.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/marcius-llmus/skills --skill react-composition-patterns-marcius-llmus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-composition-patterns
Source: https://github.com/marcius-llmus/skills/tree/main/%28architecture%29/react-composition-patterns
Command: npx skills add https://github.com/marcius-llmus/skills --skill react-composition-patterns-marcius-llmus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React composition patterns replace boolean prop proliferation with explicit variants, compound components, and context-driven state management to create scalable, reusable UI libraries.

Core Features & Use Cases

  • Explicit variant components (e.g., ThreadComposer, EditMessageComposer, ForwardMessageComposer) to replace multi-flag booleans.
  • Compound components with a shared context to compose internals without prop drilling.
  • Provider-based state management that decouples UI from data handling, enabling interchangeable backends.

Quick Start

Create explicit variant components with dedicated providers and frame-based UI composition to begin building a scalable React component library.

Frequently Asked Questions about react-composition-patterns

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

FAQPage Schema
How do I replace boolean props with React composition patterns?

React composition patterns replace boolean prop proliferation by using explicit variant components, compound components, and context providers to simplify React components.

What is the best way to structure compound components in a React design system?

Compound components in a React design system are structured using shared context to compose internals without prop drilling, decoupling UI from data handling through provider-based state management.

When do I need explicit variant components in React?

You need explicit variant components in React when scaling UI libraries or large apps requires replacing multi-flag booleans with consistent patterns for distinct component behaviors.

Can I use the React 19 use() API instead of useContext for provider-based state management?

Yes, provider-based state management in React composition patterns adheres to React 19 API guidance, utilizing the use() API over useContext to decouple UI from data handling.

How do context providers decouple UI from data handling in React architecture?

Context providers decouple UI from data handling in React architecture by enabling interchangeable backends and managing state without prop drilling, creating scalable and reusable component libraries.

Are React composition patterns suitable for large applications and UI libraries?

React composition patterns are explicitly suited for large applications and UI libraries needing consistent patterns for compound components, context providers, and scalable architecture.