The rules real projects give Cursor's agent, from .cursor/rules.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
NVIDIACursor ruleNVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/general.mdc
code, UI elements, and technical content - **Grammar and Style**: Use proper punctuation, capitalization, lists, and number formatting ### Quality Standards - **Audience-focused**: Always consider your target audience when writing - **SME Review
Steady2 mentions in 2 weeks
1 project uses a version of this
NVIDIACursor ruleNVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/writing-process.mdc
tone - Use clear, simple language - Follow formatting guidelines consistently ### After Writing - Always have content reviewed by SMEs - Test procedures with actual users when possible - Update documentation based on feedback - Keep
NVIDIACursor ruleNVIDIA/NeMo-Agent-Toolkit/.cursor/rules/nat-cli/nat-eval.mdc
Follow these rules when the user requests to evaluate a workflow
roboflowCursor ruleroboflow/inference/.cursor/rules/pr-description.mdc
Draft GitHub PR descriptions in Roboflow format (Linear link, testing, checklist). Invoke with @pr-description — not applied automatically.
No other project uses it yet
OneKeyHQCursor ruleOneKeyHQ/app-monorepo/.cursor/rules/self-testing.mdc
Mandatory self-testing checklist before completing any task — applies to all team members
Steady3 mentions in 2 weeks
No other project uses it yet
ballerine-ioCursor ruleballerine-io/ballerine/.cursor/rules/backoffice-v2.mdc
Rules and best practices for backoffice-v2 React TypeScript development
ballerine-ioCursor ruleballerine-io/ballerine/.cursor/rules/workflows-dashboard.mdc
Rules and best practices for workflows-dashboard React TypeScript development
slimm609Cursor ruleslimm609/checksec/.cursor/rules/general-rules.mdc
operations - [ ] Security implications reviewed and documented ## FINAL VERIFICATION - **ALWAYS** run security-focused code review as final step - **ALWAYS** verify no new attack vectors introduced - **ALWAYS** ensure defensive programming principles followed
MaintainerrCursor ruleMaintainerr/Maintainerr/.cursor/rules/project.mdc
Project entrypoint and standing rules
Steady3 mentions in 2 weeks
No other project uses it yet
codejunkie99Cursor rulecodejunkie99/agentic-stack/.cursor/rules/fable-grok-subagents.mdc
Model split requiring Claude Fable 5.1 selected for parent; Grok 4.6 cavecrew subagents handle bounded delegated work.
ByteDance-SeedCursor ruleByteDance-Seed/VeOmni/.cursor/rules/no-section-divider-comments.mdc
Do not use decorative section divider comments in Python code
alibabaCursor rulealibaba/loongcollector/.cursor/rules/project-knowledge/codebase-map.md
Comment/doc consistency - Comment says one behavior but code does another. - Parameter behavior change without synchronized docs update. ## 6) AI Review Priority Checklist（每次评审先扫） 1. Are lifecycle paths complete
alibabaCursor rulealibaba/loongcollector/.cursor/rules/README
用于沉淀项目级约束与知识，帮助助手在编码、评审和分析时保持一致性。 ## coding-standards/ - `cpp.mdc`：C++ 编码规范。 - `golang.mdc`：Go 编码规范。 - `commit.mdc`：提交信息规范入口。 - `compile.mdc`：编译规范入口。 ## project-knowledge/ - `architecture.md` / `architecture.mdc`：项目架构说明。 - `codebase-map.md`：代码库结构与模块分布。 - `config-pitfalls.mdc`：配置常见陷阱。 - `terminology.mdc`：术语表。 ## review-standards/ - `code-review.md` / `code-review.mdc
alibabaCursor rulealibaba/loongcollector/.cursor/rules/review-standards/code-review.md
Code Review Rule 你是一个高级代码审查助手，审查代码时要省慎仔细。 ## 1. 遇到困难的思考方式，无需输出 - 当你疑惑代码的架构设计是否合理时，你会阅读 `.cursor/rules/project-knowledge/architecture.md` 和使用Deepwiki工具了解项目全貌。 - 当你无法确定API调用的正确性时，你会阅读项目的unittest或者用context7和互联网工具查询API使用方式。 - 当你无法判断局部代码变更的正确性时，你会对修改的文件整体进行阅读，并根据函数调用关系找到依赖的文件一起阅读进行评判。 ## 2. 获取评审内容，无需输出 用户会提供分支或PR信息，请根据以下指示获取评审文件列表和内容 1. 如果提供两个分支名称（例如 "fork/feature" 和 "main"）。获取评审文件列表和内容的方法是： - 运行
alibabaCursor rulealibaba/loongcollector/.cursor/rules/utils/mermaid.mdc
Whenever diagrams or mermaid is mentioned
alibabaCursor rulealibaba/loongcollector/.cursor/rules/workflows/riper5-protocol.mdc
This workflow, known as RIPER-5, is designed exclusively for handling complex software engineering tasks such as system design, architectural refactoring, bug diagnosis, performance optimization, and multi-component integration.
zombieyangCursor rulezombieyang/sd-ppp/.cursor/rules/vite.mdc
Formatting:** - Use ESLint with recommended rulesets (e.g., `eslint:recommended`, `plugin:react/recommended`). - Use Prettier for code formatting. - Configure ESLint and Prettier to work together. - **Deployment Best Practices:** - Deploy
trycompaiCursor ruletrycompai/comp/.cursor/rules/code.mdc
Use when writing TypeScript/React code - covers type safety, component patterns, and file organization
No other project uses it yet
trycompaiCursor ruletrycompai/comp/.cursor/rules/cursor-usage.mdc
How to write and manage Cursor rules - invoke with @cursor-usage
trycompaiCursor ruletrycompai/comp/.cursor/rules/prompt-engineering.mdc
Prompt engineering best practices - invoke with @prompt-engineering
No other project uses it yet
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.
