ahmed3elshaerCursor ruleeverything-claude-code-mobile / rules
ahmed3elshaer/everything-claude-code-mobile/.cursor/rules/everything-mobile.mdc
Android, iOS, and Kotlin Multiplatform engineering guidance.
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 23Worked for most · soon
ahmed3elshaerCursor rule
TechNickAICursor ruleAICodeBot / rules
TechNickAI/AICodeBot/.cursor/rules/ai-personality.mdc
Focus on helping understand underlying principles - Be clear, patient, and encouraging in responses - When reviewing code: - Highlight errors or areas for improvement - Explain clearly why changes are needed - Offer praise
TechNickAICursor ruleAICodeBot / rules
TechNickAI/AICodeBot/.cursor/rules/python.mdc
when editing python files
TechNickAICursor ruleAICodeBot / rules
TechNickAI/AICodeBot/.cursor/rules/testing-standards.mdc
when writing tests
FmarzochiCursor ruleEGC / rules
Fmarzochi/EGC/.cursor/rules/common-agents.md
Agent orchestration: available agents, parallel execution, multi-perspective analysis
FmarzochiCursor ruleEGC / rules
Fmarzochi/EGC/.cursor/rules/common-auto-intuition.md
EGC auto-intuition -- act on intent, not keywords
FmarzochiCursor ruleEGC / rules
Fmarzochi/EGC/.cursor/rules/common-development-workflow.md
Development workflow: plan, TDD, review, commit pipeline
FmarzochiCursor ruleEGC / rules
Fmarzochi/EGC/.cursor/rules/common-git-workflow.md
Git workflow: conventional commits, PR process
kanyun-incReads credentialsCursor rulereskill / rules
kanyun-inc/reskill/.cursor/rules/development.mdc
docs/cli-spec.md`:** ``` 1. SPEC → Modify docs/cli-spec.md 2. REVIEW → PR review for spec changes 3. TEST → Write failing tests (integration + unit) 4. CODE → Implement minimal code to pass tests 5. REFACTOR → Improve
kanyun-incCursor rulereskill / rules
kanyun-inc/reskill/.cursor/rules/testing.mdc
Modify docs/cli-spec.md to define expected behavior│ │ 2. REVIEW Review spec changes │ │ 3. TEST Write failing tests based on spec (RED) │ │ 4. CODE Write minimal code to pass tests (GREEN
KanevryCursor rulesession-orchestrator / rules
Kanevry/session-orchestrator/.cursor/rules/020-quality-gates.mdc
When running quality checks — typecheck, test, lint — during development or session execution
KanevryCursor rulesession-orchestrator / rules
Kanevry/session-orchestrator/.cursor/rules/040-discovery.mdc
When the user types /discovery or requests quality analysis, code audit, or issue detection
KanevryCursor rulesession-orchestrator / rules
Kanevry/session-orchestrator/.cursor/rules/060-evolve.mdc
When the user types /evolve or asks about session learnings, pattern extraction, or learning management
KanevryCursor rulesession-orchestrator / rules
Kanevry/session-orchestrator/.cursor/rules/070-gitlab-ops.mdc
When working with GitLab or GitHub — issues, merge requests, pull requests, CI pipelines, labels
lucamezzaliraCursor rulemfe-skills / rules
lucamezzalira/mfe-skills/.cursor/rules/mfe-architecture-boundary-design.mdc
Micro-frontend architecture: Boundary design. Load when this topic is in scope; part of mfe-skills.
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.