vercel-composition-patterns

Refactor React components into compound components, render props, and context providers.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill vercel-composition-patterns-proffroggo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-composition-patterns
Source: https://github.com/ProfFroggo/froggo-mission-control/tree/main/.claude/skills/composition-patterns
Command: npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill vercel-composition-patterns-proffroggo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Guidelines for architecture, state management, and React 19 API changes to keep codebases coherent.
  • Strategies for building reusable component libraries and scalable APIs using composition.
  • When to apply these patterns: refactoring components with many boolean props and creating flexible, extensible UI.

Quick Start

Refactor a React component library to use compound components, lift state, and context providers for scalable, maintainable APIs.

Frequently Asked Questions about vercel-composition-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid boolean prop proliferation in React components?

Compound components in React let you compose complex UIs from independent child parts sharing implicit state. This pattern uses context providers to pass data internally, avoiding prop drilling and making the component API more predictable and extensible.

When should I use render props and compound components?

You refactor React components into scalable composition patterns by identifying components with excessive boolean props, extracting sub-components, lifting shared state, and connecting them via context providers to create a predictable and extensible API surface.

Does this composition pattern work with React 19 API changes?

These composition patterns are designed for building reusable React component libraries and scalable APIs. They apply to any app or library needing compound components, render props, and context providers to scale UI while preserving predictable behavior.

Why does my React component API become hard to maintain as it scales?

For large component libraries, avoid overusing render props and excessive boolean props by applying targeted compound components and context providers. Overusing these patterns can introduce unnecessary complexity when simpler component composition would suffice.