react-best-practices

react-best-practices is a cursor rule for Cursor from omergulcicek/omergulcicek.com. It costs 0 tokens per session (320 once invoked), scanned A, a copy of react-best-practices, MIT.

USE WHEN: Designing React components, implementing hooks, and managing component lifecycles.

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/omergulcicek/omergulcicek.com/react-best-practices
Clone the repo
git clone --depth 1 https://github.com/omergulcicek/omergulcicek.com

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for react-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/react-best-practices.svg)](https://agentmods.dev/rules/omergulcicek/omergulcicek.com/react-best-practices)
Your own site
<a href="https://agentmods.dev/rules/omergulcicek/omergulcicek.com/react-best-practices"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/react-best-practices.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00320
Opus 5 $0.00000 $0.00160
Sonnet 5 $0.00000 $0.00064
Haiku 4.5 $0.00000 $0.00032

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

Security

Grade A, and why

react-best-practices 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 2d ago.

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.

Origin

This is a copy

100% identical to react-best-practices — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/react-best-practices.mdc · 46 lines

What it actually says

React Best Practices

Constraints

  • SRP: Keep components small (max 200 lines).
  • Composition: Use children or slots instead of prop drilling.
  • Naming: Use PascalCase for components, useCamelCase for hooks.
  • Hooks: Move business logic to custom hooks.
  • State: Lift state to the nearest common ancestor.
  • Updates: Use setState(prev => ...) for state updates.
  • Effects: Use useEffect as a last resort. Prefer event handlers or useMemo.
  • Keys: Use stable IDs for lists (index is forbidden).

Bans

  • Prop drilling (>2 levels).
  • Class components.
  • Incomplete dependency arrays.
  • Syncing props to state (use Derived state).
  • Heavy computations during render.
  • Data fetching inside components (violation of API rules).

Correct Implementation

Incorrect Implementation

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. 2d ago First seen · 46 lines · 0 tokens per session scan A ea29de16d44e

Subscribe to this mod's changes

react-best-practices is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 320 tokens. A static security scan graded it A with 0 findings. It is 100% identical to react-best-practices, differing in 7 lines, and is treated as a copy.