What problem does it solve?
It helps teams eliminate boolean prop proliferation and tangled component logic by moving to compound components, lifted state, and explicit variants that stay maintainable as features grow.
Core Features & Use Cases
- Compound component architecture: Build reusable component “pieces” that share state via context instead of prop drilling, making composition predictable for both humans and agents.
- State lifting & provider boundaries: Move state management into provider components so UI pieces consume a stable context interface while sibling or external UI can still read actions and state.
- Explicit variants over boolean modes: Replace ambiguous combinations of boolean flags (e.g., isThread, isEditing) with self-documenting variant components like ThreadComposer and EditComposer.
- React 19 API guidance: Applies React 19+ conventions using
use() for context consumption and treating ref as a regular prop instead of relying on forwardRef.
Quick Start
Use this skill when refactoring a React UI that currently uses many boolean props or render-prop conditionals, and ask an AI to redesign it into explicit compound components with lifted provider state following the included React 19 guidance.