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.
npx agentmods add rules/thesethrose/devrules/react19git clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.
| Model | Per session | Once 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 |
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.
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, anduseMemo. - Implement cleanup logic in
useEffectfor subscriptions, timers, or other resources that need disposal.
State Management
- Use
useStatefor simple, local component state. - Use
useReducerfor 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.memoto memoize components based on prop equality. - Use
useCallbackto memoize callback functions passed to optimized child components. - Use
useMemoto memoize expensive calculations.
- Use
- Apply memoization judiciously; profile first to identify actual bottlenecks.
- Use proper
keyprops when rendering lists to help React identify items. - Use code splitting (e.g.,
React.lazywith Suspense) to lazy-load components not needed immediately. - Profile component render performance using React DevTools.
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.
- yesterday First seen · 76 lines · 873 tokens per session scan A b8d9e3aeb529
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.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.