langfuse/vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
This is a copy. The original lives at vercel-labs/sandcastle-vercel-composition-patterns.
npx skills add https://github.com/langfuse/langfuse --skill vercel-composition-patterns
Composition patterns for building flexible, maintainable React components. Avoid
boolean prop proliferation by using compound components, lifting state, and
composing internals. These patterns make codebases easier for both humans and AI
agents to work with as they scale.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
| -------- | ----------------------- | ------ | --------------- |
| 1 | Component Architecture | HIGH | architecture- |
| 2 | State Management | MEDIUM | state- |
| 3 | Implementation Patterns | MEDIUM | patterns- |
| 4 | React 19 APIs | MEDIUM | react19- |
architecture-avoid-boolean-props - Don't add boolean props to customizebehavior; use composition
architecture-compound-components - Structure complex components with sharedcontext
state-decouple-implementation - Provider is the only place that knows howstate is managed
state-context-interface - Define generic interface with state, actions, metafor dependency injection
state-lift-state - Move state into provider components for sibling accesspatterns-explicit-variants - Create explicit variant components instead ofboolean modes
patterns-children-over-render-props - Use children for composition insteadof renderX props
> ⚠️ React 19+ only. Skip this section if using React 18 or earlier.
react19-no-forwardref - Don't use forwardRef; use use() instead of useContext()Read individual rule files for detailed explanations and code examples:
rules/architecture-avoid-boolean-props.md
rules/state-context-interface.md
Each rule file contains:
For the complete guide with all rules expanded: AGENTS.md
Take langfuse/vercel-composition-patterns from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.