react-composition-patterns

A set of React design patterns for building flexible components from smaller parts. It covers compound components, shared context, state placement, render props, children, and changes in React 19.

In plain words
What is it for?
Use it when designing component libraries, refactoring components with many boolean props, sharing state between component parts, or choosing between children and render props.
Why use it?
Components with many true-or-false options often create tangled conditional code and too many combinations. Composition lets callers assemble the needed behavior more clearly.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/alonsarias/agent-rules/react-composition-patterns
Clone the repo
git clone --depth 1 https://github.com/alonsarias/agent-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,324 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03324
Opus 5 $0.00000 $0.01662
Sonnet 5 $0.00000 $0.00665
Haiku 4.5 $0.00000 $0.00332

Measured yesterday against content hash 5fa4c2a573cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react-composition-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/react-composition-patterns.mdc · 632 lines

How it starts

The opening of the file, as written. The whole thing — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.

React Composition Patterns

Composition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals.


1. Avoid Boolean Prop Proliferation

Impact: CRITICAL - Prevents unmaintainable component variants

Don't add boolean props like isThread, isEditing, isDMThread to customize behavior. Each boolean doubles possible states and creates unmaintainable conditional logic.

Incorrect: boolean props create exponential complexity

function Composer({
  onSubmit,
  isThread,
  channelId,
  isDMThread,
  dmId,
  isEditing,
  isForwarding,
}: Props) {
  return (
    <div className="composer">
      <Input />
      {isDMThread ? (
        <DMThreadHeader dmId={dmId} />
      ) : isThread ? (
        <ThreadHeader channelId={channelId} />
      ) : null}
      {isEditing ? (
        <EditActions />
      ) : isForwarding ? (
        <ForwardActions />
      ) : (
        <SendActions onSubmit={onSubmit} />
      )}
    </div>
  )
}

Correct: composition eliminates conditionals

// Channel composer
function ChannelComposer() {
  return (
    <ComposerProvider>
      <ComposerFrame>
        <ComposerInput />
        <ComposerFooter>
          <FormattingTools />
          <EmojiPicker />
          <SendButton />
        </ComposerFooter>
      </ComposerFrame>
    </ComposerProvider>
  )
}

// Thread composer - adds "also send to channel" field
function ThreadComposer({ channelId }: { channelId: string }) {
  return (
    <ThreadProvider channelId={channelId}>
      <ComposerFrame>
        <ComposerInput />
        <AlsoSendToChannel />
        <ComposerFooter>
          <FormattingTools />
          <SendButton />
        </ComposerFooter>
      </ComposerFrame>
    </ThreadProvider>
  )
}

// Edit composer - different footer actions
function EditComposer() {
  return (
    <EditProvider>
      <ComposerFrame>
        <ComposerInput />
        <ComposerFooter>
          <CancelButton />
          <SaveButton />
        </ComposerFooter>
      </ComposerFrame>
    </EditProvider>
  )
}

Read the full file on GitHub · 632 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 632 lines · 0 tokens per session scan A 5fa4c2a573cc

Subscribe to this mod's changes

react-composition-patterns is a cursor rule published in the GitHub repository alonsarias/agent-rules (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,324 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.