React19

A set of guidelines for building React user interfaces, including component structure, Hooks, state, and performance.

In plain words
What is it for?
Use it when designing components, extracting shared logic, managing state, and reviewing React application code.
Why use it?
It helps keep React code organized, reusable, and less likely to break because of incorrect Hook usage or tangled state.

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/thesethrose/devrules/react19
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/DevRules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 873 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.00873
Opus 5 $0.00000 $0.00436
Sonnet 5 $0.00000 $0.00175
Haiku 4.5 $0.00000 $0.00087

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

Security

Grade A, and why

React19 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/technologies/React19.mdc · 76 lines

How it starts

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

React Best Practices

Component Design & Structure

  • Prefer functional components with Hooks over class components.
  • Keep components small, focused, and reusable.
  • Use composition to combine components. Avoid inheritance patterns.
  • Define prop types clearly (using TypeScript interfaces/types is recommended).
  • Split large components into smaller, more manageable ones.
  • Colocate related components, hooks, and types where appropriate.

Hooks

  • Strictly follow the Rules of Hooks (only call hooks at the top level, only from React functions).
  • Extract reusable stateful logic into custom Hooks.
  • Keep custom Hooks focused on a single concern.
  • Provide exhaustive and correct dependency arrays for useEffect, useCallback, and useMemo.
  • Implement cleanup logic in useEffect for subscriptions, timers, or other resources that need disposal.

State Management

  • Use useState for simple, local component state.
  • Use useReducer for more complex state logic involving multiple sub-values or state transitions.
  • Use React Context API (useContext) for sharing state that needs to be accessible by many components at different levels, but be mindful of performance implications.
  • Keep state as close as possible to where it's needed.
  • Avoid excessive prop drilling by lifting state up or using Context/state management solutions.
  • Evaluate the need for external state management libraries carefully; often, built-in hooks and composition suffice.

Performance Optimization

  • Avoid unnecessary re-renders:
    • Use React.memo to memoize components based on prop equality.
    • Use useCallback to memoize callback functions passed to optimized child components.
    • Use useMemo to memoize expensive calculations.
  • Apply memoization judiciously; profile first to identify actual bottlenecks.
  • Use proper key props when rendering lists to help React identify items.
  • Use code splitting (e.g., React.lazy with Suspense) to lazy-load components not needed immediately.
  • Profile component render performance using React DevTools.

Read the full file on GitHub · 76 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 · 76 lines · 873 tokens per session scan A b8d9e3aeb529

Subscribe to this mod's changes

React19 is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 873 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-30.