Skills/vercel-composition-patterns
Infuseting 51a66b9575 feat(skills): add full-stack design engineering and compliance skills suite
- 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)
2026-09-19 22:12:44 +02:00
..
rules feat(skills): add full-stack design engineering and compliance skills suite 2026-09-19 22:12:44 +02:00
AGENTS.md feat(skills): add full-stack design engineering and compliance skills suite 2026-09-19 22:12:44 +02:00
README.md feat(skills): add full-stack design engineering and compliance skills suite 2026-09-19 22:12:44 +02:00
SKILL.md feat(skills): add full-stack design engineering and compliance skills suite 2026-09-19 22:12:44 +02:00
metadata.json feat(skills): add full-stack design engineering and compliance skills suite 2026-09-19 22:12:44 +02:00

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 rules
    • area-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 behavior
  • architecture-compound-components.md - Structure as compound components with shared context

State Management (HIGH)

  • state-lift-state.md - Lift state into provider components
  • state-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 props
  • patterns-explicit-variants.md - Create explicit component variants

Core Principles

  1. Composition over configuration — Instead of adding props, let consumers compose
  2. Lift your state — State in providers, not trapped in components
  3. Compose your internals — Subcomponents access context, not props
  4. Explicit variants — Create ThreadComposer, EditComposer, not Composer with isThread

Creating a New Rule

  1. Copy rules/_template.md to rules/area-description.md
  2. Choose the appropriate area prefix:
    • architecture- for Component Architecture
    • state- for State Management
    • patterns- for Implementation Patterns
  3. Fill in the frontmatter and content
  4. Ensure you have clear examples with explanations

Impact Levels

  • CRITICAL - Foundational patterns, prevents unmaintainable code
  • HIGH - Significant maintainability improvements
  • MEDIUM - Good practices for cleaner code