- Add UI/UX design & anti-slop skills (frontend-design, ui-ux-pro-max, tailwind-design-system, shadcn) - Add 3D creative skills (threejs suite, canvas-design, algorithmic-art) - Add React 19 architecture & performance skills (vercel composition & best practices) - Add zero-CLS skeleton contract (component-skeleton-contract) - Add resilient forms, type-safe data fetching, and i18n/l10n standards - Add security, performance, and legal compliance (web-appsec-hardening, web-vitals-performance, eu-legal-compliance, e2e-a11y-testing) |
||
|---|---|---|
| .. | ||
| rules | ||
| AGENTS.md | ||
| README.md | ||
| SKILL.md | ||
| metadata.json | ||
README.md
React Composition Patterns
A structured repository for React composition patterns that scale. These patterns help avoid boolean prop proliferation by using compound components, lifting state, and composing internals.
Structure
rules/- Individual rule files (one per rule)_sections.md- Section metadata (titles, impacts, descriptions)_template.md- Template for creating new rulesarea-description.md- Individual rule files
metadata.json- Document metadata (version, organization, abstract)AGENTS.md- Compiled output (generated)
Rules
Component Architecture (CRITICAL)
architecture-avoid-boolean-props.md- Don't add boolean props to customize behaviorarchitecture-compound-components.md- Structure as compound components with shared context
State Management (HIGH)
state-lift-state.md- Lift state into provider componentsstate-context-interface.md- Define clear context interfaces (state/actions/meta)state-decouple-implementation.md- Decouple state management from UI
Implementation Patterns (MEDIUM)
patterns-children-over-render-props.md- Prefer children over renderX propspatterns-explicit-variants.md- Create explicit component variants
Core Principles
- Composition over configuration — Instead of adding props, let consumers compose
- Lift your state — State in providers, not trapped in components
- Compose your internals — Subcomponents access context, not props
- Explicit variants — Create ThreadComposer, EditComposer, not Composer with isThread
Creating a New Rule
- Copy
rules/_template.mdtorules/area-description.md - Choose the appropriate area prefix:
architecture-for Component Architecturestate-for State Managementpatterns-for Implementation Patterns
- Fill in the frontmatter and content
- Ensure you have clear examples with explanations
Impact Levels
CRITICAL- Foundational patterns, prevents unmaintainable codeHIGH- Significant maintainability improvementsMEDIUM- Good practices for cleaner code