vercel-composition-patterns

To avoid boolean prop proliferation in React components, replace monolithic components with explicit variant components like ThreadComposer or EditMessageComposer, ensuring clearer behavior and safer UI architecture.

Use compound components with shared context in React by composing small, reusable UI pieces that share state via a single context provider, avoiding prop drilling and ensuring scalable component architectures.

Yes, you can use the React 19 use() hook instead of useContext for state management. This Skill enforces React 19 API guidance, applying the use() hook for safer, scalable context provider patterns.

The best way to refactor a React component library for scalability is introducing explicit variant components and a shared Composer.Provider, then assembling the UI with small pieces like Frame, Input, and Submit.

Lift state into providers so sibling components and external UI can access and modify state without threading props. This shared provider pattern centralizes state management for safer React architectures.