f5792c40be
Pulled ALL skills from 15 source repositories: - anthropics/skills: 16 (docs, design, MCP, testing) - obra/superpowers: 14 (TDD, debugging, agents, planning) - coreyhaines31/marketingskills: 25 (marketing, CRO, SEO, growth) - better-auth/skills: 5 (auth patterns) - vercel-labs/agent-skills: 5 (React, design, Vercel) - antfu/skills: 16 (Vue, Vite, Vitest, pnpm, Turborepo) - Plus 13 individual skills from various repos Mosaic Stack is not limited to coding — the Orchestrator and subagents serve coding, business, design, marketing, writing, logistics, analysis, and more. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
61 lines
2.1 KiB
Markdown
61 lines
2.1 KiB
Markdown
# 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
|