.cursor/skills/composition-patterns/SKILL.md
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.
npx skillsauth add alexwox/genesis-template vercel-composition-patternsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 customize
behavior; use compositionarchitecture-compound-components - Structure complex components with shared
contextstate-decouple-implementation - Provider is the only place that knows how
state is managedstate-context-interface - Define generic interface with state, actions, meta
for dependency injectionstate-lift-state - Move state into provider components for sibling accesspatterns-explicit-variants - Create explicit variant components instead of
boolean modespatterns-children-over-render-props - Use children for composition instead
of 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
tools
Translate role-based organizations into workflow-based organizations by decomposing roles into scored tasks, extracting dark playbooks (proprietary tacit knowledge), formalizing workflows, calculating automation ROI, and producing a sequenced automation roadmap. Use when a company wants to identify what work can be automated, extract undocumented expert knowledge, or build an automation strategy.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
Builds stakeholder-friendly project status updates from markdown sources. Use when asked for progress reports, implementation status, future plans, UI/UX flow summaries, infrastructure/data-flow summaries, risks, code smells, or scout-principle improvement notes.
development
Repeatable playbook for finding and interviewing key stakeholders to validate an offer pillar hypothesis. Produces a pain proximity map, target list, outreach plan, interview protocol, and structured synthesis of findings. Use when a hypothesis needs human validation before building.