react-advanced-patterns

A set of React techniques for handling refs, event callbacks, subscriptions, effects, and app startup. It focuses on cases where components need stable references or one-time initialization.

In plain words
What is it for?
Use it when managing event-handler refs, effect dependencies, subscriptions, stable callbacks, or initialization that should happen once when the app starts.
Why use it?
React components can run setup code again when they remount, especially during development, and changing callback references can cause unnecessary work. These patterns help keep setup and event handling predictable.

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-advanced-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 1,476 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.01476
Opus 5 $0.00000 $0.00738
Sonnet 5 $0.00000 $0.00295
Haiku 4.5 $0.00000 $0.00148

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

Security

Grade A, and why

react-advanced-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-advanced-patterns.mdc · 257 lines

How it starts

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

React Advanced Patterns

Advanced patterns for specific cases requiring careful implementation.

1. Initialize App Once, Not Per Mount

Impact: LOW-MEDIUM - Avoids duplicate initialization in development

Don't put app-wide initialization inside useEffect([]). Components can remount (especially in React StrictMode), causing effects to re-run. Use a module-level guard instead.

Incorrect: runs twice in dev, re-runs on remount

function App() {
  useEffect(() => {
    loadFromStorage()
    checkAuthToken()
    initializeAnalytics()
  }, [])

  return <MainContent />
}

Correct: once per app load

let didInit = false

function App() {
  useEffect(() => {
    if (didInit) return
    didInit = true

    loadFromStorage()
    checkAuthToken()
    initializeAnalytics()
  }, [])

  return <MainContent />
}

Alternative: initialize outside component

// Initialize at module level (runs once when module loads)
loadFromStorage()
checkAuthToken()
initializeAnalytics()

function App() {
  return <MainContent />
}

Alternative: use a dedicated initialization module

// init.ts
let initialized = false

export function initApp() {
  if (initialized) return
  initialized = true

  loadFromStorage()
  checkAuthToken()
  initializeAnalytics()
}

// App.tsx
import { initApp } from './init'

initApp() // Called once at module load

function App() {
  return <MainContent />
}

Reference: Initializing the application


2. Store Event Handlers in Refs

Impact: LOW - Stable subscriptions

Store callbacks in refs when used in effects that shouldn't re-subscribe on callback changes.

Incorrect: re-subscribes on every render

function useWindowEvent(event: string, handler: (e: Event) => void) {
  useEffect(() => {
    window.addEventListener(event, handler)
    return () => window.removeEventListener(event, handler)
  }, [event, handler]) // handler changes every render
}

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

Subscribe to this mod's changes

react-advanced-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 1,476 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.