CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-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.

77

1.43x
Quality

72%

Does it follow best practices?

Impact

99%

1.43x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/react-composition-patterns/skills/react-composition-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

React 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.

When to Apply

Reference these guidelines when:

  • Refactoring components with many boolean props
  • Building reusable component libraries
  • Designing flexible component APIs
  • Reviewing component architecture
  • Working with compound components or context providers

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Component ArchitectureHIGHarchitecture-
2State ManagementMEDIUMstate-
3Implementation PatternsMEDIUMpatterns-

Quick Reference

1. Component Architecture (HIGH)

  • architecture-avoid-boolean-props - Don't add boolean props to customize behavior; use composition
  • architecture-compound-components - Structure complex components with shared context

2. State Management (MEDIUM)

  • state-decouple-implementation - Provider is the only place that knows how state is managed
  • state-context-interface - Define generic interface with state, actions, meta for dependency injection
  • state-lift-state - Move state into provider components for sibling access

3. Implementation Patterns (MEDIUM)

  • patterns-explicit-variants - Create explicit variant components instead of boolean modes
  • patterns-children-over-render-props - Use children for composition instead of renderX props

How to Use

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:

  • Brief explanation of why it matters
  • Incorrect code example with explanation
  • Correct code example with explanation
  • Additional context and references

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Repository

secondsky/claude-skills

Path

plugins/react-composition-patterns/skills/react-composition-patterns/SKILL.md

Last updated
First committed

Also appears in

langfuse/langfuse
Modified

on Oct 20, 2026

Renamed to: vercel-composition-patterns

dtyq/magic
Modified

on Oct 11, 2026

Renamed to: vercel-composition-patterns

compozy/compozy
Modified

on Sep 24, 2026

Renamed to: vercel-composition-patterns

AzizBelhassan/timeverse
Modified

on Aug 28, 2026

Renamed to: vercel-composition-patterns

whimzyLive/nightshift-ai
Modified

on Aug 7, 2026

Renamed to: vercel-composition-patterns

Draculabo/AntigravityManager
Modified

on Jul 28, 2026

Renamed to: vercel-composition-patterns

Draculabo/AntigravityManager
Modified

on Jul 28, 2026

Renamed to: vercel-composition-patterns

openstatusHQ/data-table-filters
Modified

on Jul 27, 2026

Renamed to: vercel-composition-patterns

zebbern/claude-code-guide
Modified

on Jul 24, 2026

Renamed to: vercel-composition-patterns

1weiho/open-slide
Modified

on Jul 24, 2026

Renamed to: vercel-composition-patterns

JetBrains/skills
Modified

on Jul 17, 2026

Renamed to: vercel-composition-patterns

databricks/devhub
Modified

on May 6, 2026

Renamed to: vercel-composition-patterns

tech-leads-club/agent-skills
Modified

on Apr 6, 2026

vercel-labs/agent-skills
Modified

on Mar 2, 2026, based on e7a744f

Renamed to: vercel-composition-patterns

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.