vercel-composition-patterns

Refactors React components using compound components, context providers, and composition patterns.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Alwahdi/mikrotik-whisperer --skill vercel-composition-patterns-alwahdi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-composition-patterns
Source: https://github.com/Alwahdi/mikrotik-whisperer/tree/main/.agents/skills/vercel-composition-patterns
Command: npx skills add https://github.com/Alwahdi/mikrotik-whisperer --skill vercel-composition-patterns-alwahdi

SYSTEM DOCUMENTATION & REQUIREMENTS

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. ## Core Features & Use Cases - Compound Component Patterns: 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 UI components work with any provider implementation. - React 19 API Guidance: Replace forwardRef with ref-as-prop and useContext with the use() hook. - Use Case: When refactoring a Composer component overloaded with boolean flags, apply these rules to split it into explicit variants like ThreadComposer and EditComposer sharing 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 a pattern where a parent component shares state via context with its subcomponents, such as Composer.Frame, Composer.Input, and Composer.Submit. Consumers compose exactly the pieces they need without prop drilling or hidden conditionals.

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 forwardRef still work in React 19?

In React 19, ref is a regular prop, so forwardRef is no longer needed. You can also replace useContext with the use() hook, which additionally supports conditional calls.

When should I lift state into a provider component?

Lift state into a provider when sibling components outside the main UI need access to that state or its actions. This avoids prop drilling, useEffect syncing, and ref-based workarounds while keeping UI decoupled from state implementation.