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-basics-componentsgit 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.00707 |
| Opus 5 | $0.00000 | $0.00353 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
react-basics-components 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React 组件规范 (Components)
本规则由
@react-basics引用
项目结构
Create React App 布局
react_project/
├── src/
│ ├── components/ # 可复用组件 (Button/, Input/, Modal/)
│ ├── pages/ # 页面组件
│ ├── hooks/ # 自定义 Hooks
│ ├── contexts/ # React Context
│ └── utils/
Next.js 结构
nextjs_project/
├── pages/ # Pages Router
│ ├── _app.js
│ └── api/ # API 路由
├── components/
└── lib/
App Router (Next.js 13+)
nextjs_app_router/
├── app/
│ ├── layout.js
│ ├── page.js
│ └── api/
├── components/
└── lib/
函数组件 (推荐)
const TodoItem = ({ todo, onToggle, onDelete }) => (
<div className={`todo-item ${todo.completed ? 'completed' : ''}`}>
<input type="checkbox" checked={todo.completed} onChange={() => onToggle(todo.id)} />
<span>{todo.title}</span>
<button onClick={() => onDelete(todo.id)}>删除</button>
</div>
)
TodoItem.propTypes = {
todo: PropTypes.shape({
id: PropTypes.number.isRequired,
title: PropTypes.string.isRequired,
completed: PropTypes.bool.isRequired,
}).isRequired,
onToggle: PropTypes.func.isRequired,
onDelete: PropTypes.func.isRequired,
}
类组件 (生命周期/复杂状态时)
class TodoList extends Component {
state = { todos: [], filter: 'all' }
componentDidMount() {
const saved = localStorage.getItem('todos')
if (saved) this.setState({ todos: JSON.parse(saved) })
}
componentDidUpdate(prevProps, prevState) {
if (prevState.todos !== this.state.todos) {
localStorage.setItem('todos', JSON.stringify(this.state.todos))
}
}
handleAddTodo = (title) => {
this.setState(prev => ({
todos: [...prev.todos, { id: Date.now(), title, completed: false }]
}))
}
render() {
const filtered = this.getFilteredTodos()
return (
<div className="todo-list">
<TodoForm onSubmit={this.handleAddTodo} />
<ul>{filtered.map(todo => <TodoItem key={todo.id} todo={todo} ... />)}</ul>
</div>
)
}
}
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 · 112 lines · 0 tokens per session scan A 430de9bed9f8
react-basics-components 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 707 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
general
Wonder Blocks design system conventions, component patterns, and coding standards.
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.