react-rerender-optimization

A set of React techniques for reducing unnecessary component re-renders. React is a JavaScript library for building user interfaces, and a re-render is when it recalculates a component's output.

In plain words
What is it for?
Choose between state, derived values, refs, memoization, callbacks, and effects when React components update too often or have dependency and stale-closure problems.
Why use it?
It helps avoid repeated calculations, stale values, extra subscriptions, and sluggish interfaces caused by inefficient state or callback handling.

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-rerender-optimization
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,131 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.03131
Opus 5 $0.00000 $0.01566
Sonnet 5 $0.00000 $0.00626
Haiku 4.5 $0.00000 $0.00313

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

Security

Grade A, and why

react-rerender-optimization 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-rerender-optimization.mdc · 517 lines

How it starts

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

React Re-render Optimization

Patterns for reducing unnecessary re-renders to minimize wasted computation and improve UI responsiveness.

1. Calculate Derived State During Rendering

Impact: MEDIUM - Avoids redundant renders and state drift

If a value can be computed from current props/state, derive it during render instead of storing in state.

Incorrect: redundant state and effect

function Form() {
  const [firstName, setFirstName] = useState('First')
  const [lastName, setLastName] = useState('Last')
  const [fullName, setFullName] = useState('')

  useEffect(() => {
    setFullName(firstName + ' ' + lastName)
  }, [firstName, lastName])

  return <span>{fullName}</span>
}

Correct: derive during render

function Form() {
  const [firstName, setFirstName] = useState('First')
  const [lastName, setLastName] = useState('Last')
  const fullName = firstName + ' ' + lastName

  return <span>{fullName}</span>
}

Reference: You Might Not Need an Effect


2. Defer State Reads to Usage Point

Impact: MEDIUM - Avoids unnecessary subscriptions

Don't subscribe to dynamic state if you only read it inside callbacks.

Incorrect: subscribes to all searchParams changes

function ShareButton({ chatId }: { chatId: string }) {
  const searchParams = useSearchParams()

  const handleShare = () => {
    const ref = searchParams.get('ref')
    shareChat(chatId, { ref })
  }

  return <button onClick={handleShare}>Share</button>
}

Correct: reads on demand, no subscription

function ShareButton({ chatId }: { chatId: string }) {
  const handleShare = () => {
    const params = new URLSearchParams(window.location.search)
    const ref = params.get('ref')
    shareChat(chatId, { ref })
  }

  return <button onClick={handleShare}>Share</button>
}

3. Avoid useMemo for Simple Expressions

Impact: LOW-MEDIUM - Wasted computation on every render

Read the full file on GitHub · 517 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 · 517 lines · 0 tokens per session scan A ef8146c0453a

Subscribe to this mod's changes

react-rerender-optimization 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,131 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.