vercel-composition-patterns

Guides React component refactoring using compound components, context providers, and composition patterns.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/po4yka/blog --skill vercel-composition-patterns-po4yka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-composition-patterns
Source: https://github.com/po4yka/blog/tree/main/.agents/skills/composition-patterns
Command: npx skills add https://github.com/po4yka/blog --skill vercel-composition-patterns-po4yka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? React components often accumulate boolean props like isThread or isEditing, creating exponential state combinations and unmaintainable conditional logic. This Skill provides structured rules for replacing prop proliferation with composition patterns that scale. ## Core Features & Use Cases - Compound Component Architecture: Structure complex components with shared context so consumers compose exactly the pieces they need. - State Lifting & Dependency Injection: Define generic context interfaces (state, actions, meta) so the same UI works with any provider implementation. - React 19 API Guidance: Apply modern patterns like ref as a regular prop and use() instead of useContext(). - Use Case: When refactoring a message composer with six boolean props, apply these rules to split it into explicit variants like ThreadComposer and EditComposer that share compound internals. ## Quick Start Ask the AI to refactor a React component with many boolean props using the composition patterns in this skill.

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?

Replace boolean props with composition by creating explicit variant components like ThreadComposer or EditComposer. Each variant composes shared compound component pieces instead of passing conditional flags to one monolithic component.

What are compound components in React?

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.

Should I use children or render props for React composition?

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.

Does React 19 still require forwardRef?

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.

How do I share React state between sibling components without prop drilling?

Lift state into a provider component that wraps the siblings. Any component inside the provider boundary can access state and actions via context, even if it is not visually nested inside the main UI.