nextify-limitedCursor rulelibra / rules
nextify-limited/libra/.cursor/rules/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.
Cursor rules examples
The rules real projects give Cursor's agent, from .cursor/rules.
Your trail
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.
Best matches · from page 2Worked for most · soon
nextify-limitedCursor rule
tounsilsCursor ruleclaude-code-skills / rules
tounsils/claude-code-skills/.cursor/rules/review-diff.mdc
Review uncommitted or branch-local changes for defects, ranked by severity, with a concrete failure scenario behind every finding. Use when asked to review code, review a diff, review my changes, check this before I commit, look over this branch, or do a pre-PR pass. Reviews the change, not the whole repository.
raye-dengCursor ruleopen-code-review / rules
raye-deng/open-code-review/.cursor/rules/open-code-review.mdc
Open Code Review - AI code quality gate for detecting hallucinated packages, stale APIs, context breaks, security anti-patterns, and over-engineering in AI-generated code.
trypostitCursor ruletrypost / rules
trypostit/trypost/.cursor/rules/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.
brianwestphalCursor ruleglassbox / rules
brianwestphal/glassbox/.cursor/rules/glassbox.mdc
Read the latest Glassbox code review and apply all feedback annotations
rlaopeCursor rulenen / rules
rlaope/nen/.cursor/rules/nen-transmuter.mdc
Behavior-preserving refactoring under characterization tests, plus severity-rated code review. Use when the user says \"refactor\", \"clean up\", \"tech debt\", \"code review\", \"extract\", \"rename\", \"restructure\", \"this file is a mess\", or \"impossible to modify\"; when every small change breaks something unrelated; when cleanup has to land before the next feature has anywhere to go; when code is called hard to change, scary to touch, or too tangled to test; when requirements shifted and the current shape fights the new feature; when a PR needs review for structure and maintainability; or when every small change keeps ballooning because everything touches everything.
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/system-design-edho-ferdian.mdc
Mid-project architectural decision-making — Architecture Decision Records (ADRs), structured trade-off analysis, non-functional-requirements review, and scaling-tier planning for an existing system. Use for \"desain arsitektur\", \"keputusan teknis besar\", \"bikin ADR\", \"trade-off antara X dan Y\", \"should I refactor this to microservices/monolith/event-driven\", a scaling or capacity question, or any task from dev-kickoff-edho-ferdian that surfaces an uncovered ARCHITECTURE decision mid-project (not at kickoff — kickoff's own PDR process in Phase 0/1 handles that). Not for restating a single task's plan (that's dev-kickoff's PLAN stage) and not for reviewing code that already exists (that's code-review-edho-ferdian's Blueprint/Consistency domain).
streamshubCursor rulestreamshub-mcp / rules
streamshub/streamshub-mcp/.cursor/rules/code-review.mdc
Code review checklist for StreamsHub MCP pull requests
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/performance-audit-edho-ferdian.mdc
Measure-then-fix performance workflow — runs real profiling/measurement tooling (Lighthouse, bundle analyzers, heap-snapshot diffing, Node/browser profilers, DB EXPLAIN) to get a baseline, diagnoses against Core Web Vitals budgets and algorithmic-complexity patterns, applies a fix, then re-measures the delta against the budget. Use this whenever someone reports that something is slow — a page, endpoint, query, build or job — and wants it diagnosed or fixed, even when the slow code is already open and the cause looks obvious from reading it: the obvious suspect is often not where the time goes, and the baseline-then-re-measure loop is what proves a fix worked. Triggers: \"app terasa lambat\", \"kenapa lemot\", \"lama banget kebukanya\", \"optimize performance\", \"reduce bundle size\", \"find memory leak\", \"Lighthouse audit\", \"why is this slow\". Not for flagging code nobody reported as slow — that is code review (see the scope note below for the boundary with code-review-edho-ferdian's PERF domain).
Hugging FaceCursor rulenanotron / rules
huggingface/nanotron/.cursor/rules/philosophy.mdc
Core development principles and workflow for the Nanotron project. Apply when discussing project architecture, planning new features, or reviewing code structure.
Small-snakeCursor ruleandroid-code-review-skills / rules
Small-snake/android-code-review-skills/.cursor/rules/android-code-review-skills.mdc
Review local Android diffs with android-code-review-skills.
chimera-defiCursor ruleeth2-quickstart / rules
chimera-defi/eth2-quickstart/.cursor/rules/code-review.mdc
Mandatory multi-pass code review before completing any task
golid-aiCursor rulegolid / rules
golid-ai/golid/.cursor/rules/audit-bugs.mdc
Bug audit checklist — use when asked to review code for bugs, security issues, or quality problems
aborroyCursor ruleaiup-alfresco / rules
aborroy/aiup-alfresco/.cursor/rules/aiup-alfresco.mdc
AIUP Alfresco extension conventions — read AGENTS.md and command specs before generating or reviewing code
neomatrix369Cursor ruleAgentVetter / rules
neomatrix369/AgentVetter/.cursor/rules/code-review-graph.mdc
Prefer code-review-graph MCP tools before Grep/Glob/Read when exploring or reviewing this codebase
Seriora-ResearchCursor ruleseri-agent / rules
Seriora-Research/seri-agent/.cursor/rules/code-quality.mdc
Code-quality rules (Karpathy guidelines) for writing, editing, or reviewing code.
lucamezzaliraCursor rulemfe-skills / rules
lucamezzalira/mfe-skills/.cursor/rules/mfe-boundary-code-patterns.mdc
MFE boundary review: Code generation patterns by rule. Load when this topic is in scope; part of mfe-skills.
allenaiCursor ruleolmoearth_pretrain / rules
allenai/olmoearth_pretrain/.cursor/rules/pr-review.mdc
when someone asks you to do a PR review of code, pull request review, review this, or check a PR
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/respond-review.mdc
Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.
KangaKodeCursor ruleuniversal-agent-bootstrap / rules
KangaKode/universal-agent-bootstrap/.cursor/rules/code-reviewer.mdc
Code review quality gate — enforces architecture, code quality, and security conventions. Use proactively after any code change.
About cursor rules
What are cursor rules?
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
How are they different from AGENTS.md?
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
How do I use one?
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Which ones worked?
Open a rule to see its discussion. Reports from people and their agents are coming.