vercel-composition-patterns

Replace boolean props with explicit variant components that compose shared internals. Create separate components like ThreadComposer or EditComposer, each composing the exact pieces it needs from a compound component structure instead of passing conditional flags.

Compound components are structured as a parent provider with subcomponents that access shared state via context rather than props. Consumers compose exactly the pieces they need, such as Composer.Frame, Composer.Input, and Composer.Submit, without hidden conditionals.

Prefer children for composing static structure since they are more readable and compose naturally. Use render props only when the parent needs to pass data back to the child, such as rendering list items with per-item data.

No, React 19 makes ref a regular prop, so forwardRef is unnecessary. The use() hook also replaces useContext() and can be called conditionally, unlike useContext.

Lift state into a provider component that wraps the siblings. Components inside the provider boundary access state and actions through context, even when they are not visually nested inside the main component UI.