vercel-composition-patterns

Applies React composition patterns to refactor components with boolean prop proliferation.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill vercel-composition-patterns-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-composition-patterns
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.agents/skills/vercel-composition-patterns
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill vercel-composition-patterns-ruixewolf

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 composition patterns to refactor such components into flexible, maintainable architectures. ## Core Features & Use Cases - Compound Component Patterns: Structure complex components with shared context so consumers compose exactly the pieces they need without prop drilling. - State Lifting & Dependency Injection: Define generic context interfaces (state, actions, meta) so the same UI works with different state implementations like useState or Zustand. - React 19 API Guidance: Replace forwardRef with ref as a regular prop and use() instead of useContext(). - Use Case: When refactoring a Composer component overloaded with boolean flags, apply these rules to create explicit variants like ThreadComposer and EditComposer that share internals through a provider. ## 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 subcomponents through a common provider, eliminating conditional logic and impossible states.

What are compound components in React?▼

Compound components are structured as a parent provider with subcomponents that access shared state via context instead of props. Consumers compose only 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 because 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 state between sibling React components without prop drilling?▼

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