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.
MANVENDRA-githubCursor ruleMANVENDRA-github/agentry/.cursor/rules/code-review.mdc
Self-review discipline for in-conversation use — apply before declaring code complete or before committing. Walks correctness, security, maintainability, and convention checks at the time of writing. For focused review of a large diff in a fresh context, delegate to the code-reviewer agent.
Often used withadd-new-model
BambooGapCursor ruleBambooGap/skills-orchestrator/.cursor/rules/pr-review.mdc
--- id: pr-review name: PR Review summary: "Systematic PR review process with blocking/suggestion/nit severity
alibabaCursor rulealibaba/loongcollector/.cursor/rules/review-standards/code-review.mdc
Code Review Rule. Use this rule when you need expert code review for quality, security, and maintainability. This rule should be used proactively after writing logical chunks of code, before merging pull requests, or when explicitly asked to review code. Example: After implementing a new feature in a Go plugin, use this rule to review the code for potential issues. Example: When asked '请对 PR 1234 进行代码评审', 'Code Review fork/feature/x', '将 fork/feature/x 对比 main 进行CR' use this rule to perform a thorough security-focused review.
temporalioCursor ruletemporalio/temporal/.cursor/rules/review.mdc
Code review guidelines - apply when reviewing code or suggesting changes
No other project uses it yet
MANVENDRA-githubCursor ruleMANVENDRA-github/agentry/.cursor/rules/security-review.mdc
Self-review security discipline applied while writing — walk the threat model of the change (untrusted input, authz, secrets, crypto, dependencies) before handing it off. Invoke before declaring security-relevant code complete or committing it. The in-conversation companion to the security-reviewer agent; for a focused pass on a large diff in fresh context, delegate to that agent.
Often used withdependency-cve-sweepagent-sortbrand-discovery
TencentCursor ruleTencent/LoopForge/.cursor/rules/code-review.mdc
代码审查规则：审查维度、严重等级判定、报告格式。由 code-reviewer agent 在 CODE-REVIEW 阶段加载。
openshiftCursor ruleopenshift/hypershift/.cursor/rules/code-review.mdc
Code Review Rules
edhoferdianCursor ruleedhoferdian/EEF/.cursor/rules/language-code-review-edho-ferdian.mdc
Language- and framework-specific code review lenses layered on top of the general four-domain review in code-review-edho-ferdian — idioms, framework security misconfigurations, ORM/query correctness, performance traps, and testing conventions, auto-detected across ~20 stacks (React, Python, Go, Java/Spring, Ruby, and more — see the reference table below for the full list). Use whenever a review touches a specific language/framework and the generic checklist isn't enough — \"review kode Go/Python/React ini\", \"audit Django models\", \"cek FastAPI endpoint ini\", or when the user names a stack while asking for review. Load it for any review of code in a named framework, even one or two files: its per-stack lenses carry the framework misconfigurations and ORM query traps that a generic read of the code misses. Loads only the lens file(s) matching the detected stack. Inherits Reflection and Critique-Correction gates from code-review-edho-ferdian.
carmentacollectiveCursor rulecarmentacollective/carmenta/.cursor/rules/code-review-standards.mdc
When doing code reviews
galyarderlabsCursor rulegalyarderlabs/galyarder-framework/.cursor/rules/code-reviewer.mdc
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
MicrosoftCursor rulemicrosoft/data-formulator/.cursor/rules/implementation-review-checklist.mdc
Require structural code review after implementation before final response
edhoferdianCursor ruleedhoferdian/EEF/.cursor/rules/frontend-engineering-edho-ferdian.mdc
Authoring and configuration guidance for building React/Next.js frontend applications well from the start — component composition, UX/interaction recipes, Vite config, HeroUI setup, and AI-slop detection (see the Reference files table below for the full breakdown). A companion to language-code-review-edho-ferdian (which reviews code after it's written) — use this when DESIGNING or WRITING new frontend code, not when reviewing existing code. Trigger phrases: \"bagaimana cara structure component ini\", \"best practice React untuk X\", \"setup Vite untuk Y\", \"biar UI-nya gak keliatan AI banget\", \"kok hasil desainnya generic/template banget\", or when starting a new frontend feature.
alexandrershovCursor rulealexandrershov/assumption-checkpoint-skill/.cursor/rules/assumption-checkpoint.mdc
Use Assumption Checkpoint when diagnosing bugs, changing code, reviewing code, explaining unfamiliar code, making implementation decisions, or calling work complete.
vibeevalReads credentialsCursor rulevibeeval/vibecosystem/.cursor/rules/security.mdc
Security rules for code review and vulnerability prevention
appsmithorgCursor ruleappsmithorg/appsmith/.cursor/rules/quality/performance-optimizer.mdc
Performance anti-patterns to watch for in JS/TS, Java, and CSS code reviews
No other project uses it yet
Surya8991Cursor ruleSurya8991/AgentMaster/.cursor/rules/codereview.mdc
Blunt, factual code review. No sugar coating. Finds bugs, security issues, performance problems, and architecture flaws. Use when user says /codereview or asks to review code.
vikisingh23Cursor rulevikisingh23/neuraforge-ai/.cursor/rules/code-review.mdc
NeuraForge AI — code-review
danielvm-gitCursor ruledanielvm-git/bigpowers/.cursor/rules/request-review.mdc
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.
d3georgeCursor ruled3george/slash-admin/.cursor/rules/common/clean-code.mdc
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
andr-caCursor ruleandr-ca/agentharness/.cursor/rules/code-review-db.mdc
Use when reviewing code that touches the database or persistence layer. Covers index strategy, query count, N+1, transaction scope, migration safety, and connection pooling. Load instead of the general code-review skill for DB-focused reviews.
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.
