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/wangqiqi/cursor-ai-rules/react-advanced-practicesgit clone --depth 1 https://github.com/wangqiqi/cursor-ai-rulesWhat 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.00508 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
react-advanced-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.
What it actually says
React 最佳实践 (Best Practices)
本规则由
@react-advanced引用
文件组织
src/
├── components/
│ ├── ui/ # 基础 UI 组件
│ ├── forms/ # 表单组件
│ ├── layout/ # 布局组件
│ └── common/ # 通用组件
├── pages/
├── hooks/
├── contexts/
├── utils/
├── services/
└── types/
命名约定
| 类型 | 约定 | 示例 |
|---|---|---|
| 组件文件 | PascalCase | UserProfile.jsx |
| Hook 文件 | camelCase | useAuth.js |
| 事件处理器 | handle + PascalCase | handleSubmit |
| 自定义 Hook | use + PascalCase | useUserProfile |
组件设计模式
高阶组件 (HOC)
function withLoading(Component) {
return function WrappedComponent({ loading, ...props }) {
if (loading) return <div>加载中...</div>
return <Component {...props} />
}
}
Render Props
<DataProvider url="/api/users">
{({ data, loading, error }) => {
if (loading) return <div>加载中...</div>
if (error) return <div>错误</div>
return <ul>{data.map(u => <li key={u.id}>{u.name}</li>)}</ul>
}}
</DataProvider>
Compound Components
const Tabs = ({ children }) => {
const [activeTab, setActiveTab] = useState(0)
return React.Children.map(children, (child, i) =>
React.cloneElement(child, { isActive: i === activeTab, onClick: () => setActiveTab(i) })
)
}
原则
- MUST 优化组件渲染性能
- DO NOT 忽略可访问性 (a11y)
- ALWAYS 测试组件行为
引用: @react-advanced
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.
- 2d ago First seen · 80 lines · 0 tokens per session scan A 036363c5e45c
react-advanced-practices is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (15 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 508 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
react-vite-web
Cursor rule "react-vite-web" from WellApp-ai/Well, covering web rules (react + vite), routing, component structure, state management and api integration.
frontend-patterns
React/TypeScript patterns for src/ code.
new-component
Workflow for creating new React components.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
performance-optimization-rule
Rules to optimize performance of React and TypeScript components.
nextjs
Next.js 16 App Router Standards & Constraints.