hyperb1issCursor ruledroidmind / rules
hyperb1iss/droidmind/.cursor/rules/003_cursor_docs.mdc
Description: These files contain reference documentation and guides to aid in development efforts for the DroidMind project
Cursor rules examples
The rules real projects give Cursor's agent, from .cursor/rules.
Best matches · from page 3Worked for most · soon
hyperb1issCursor rule
vypdevCursor rulecopilot / rules
vypdev/copilot/.cursor/rules/project-context.mdc
Current repository context, commands, and documentation authority
coddy-projectCursor rulecoddy-agent / rules
coddy-project/coddy-agent/.cursor/rules/russian-wording.mdc
Russian wording for agent-related text (UI dictionaries, documentation, answers)
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/docs-sync-edho-ferdian.mdc
Keep USER-FACING documentation honest against the current codebase — README, docs/CODEMAPS/*, architecture-as-markdown, public API docs. Generates/refreshes codemaps and validates doc freshness (every path exists, every link resolves, every code snippet matches reality, timestamps are current). Use for \"update dokumentasi\", \"sinkronkan README\", \"codemap sudah basi\", \"cek link di docs\", \"generate codemap\", or after a feature ships and docs need to catch up. Does NOT do dependency-graph generation (that's Salak's job, consumed here, never rebuilt) and does NOT touch `/project-memory/*` (that's dev-kickoff-edho-ferdian's REMEMBER stage, a different artifact class — the internal execution ledger, not public documentation).
aiurdaCursor ruledevcontext / rules
aiurda/devcontext/.cursor/rules/010-documentation-context.mdc
Require using Context7 or Web Search to review library documentation before implementation
oniharnantyoCursor rulego-ai-ready-boilerplate / rules
oniharnantyo/go-ai-ready-boilerplate/.cursor/rules/07-documentation.mdc
Documentation rules; AGENTS.md and CLAUDE.md stay minimal
NVIDIACursor rulephysicsnemo / rules
NVIDIA/physicsnemo/.cursor/rules/mod-003b-docstring-must-use-raw-string-prefix.mdc
Model and method docstrings must be prefixed with r""" (raw string with triple double quotes) for proper LaTeX rendering in Sphinx documentation.
cbtw-apacCursor ruleqdrant-loader / rules
cbtw-apac/qdrant-loader/.cursor/rules/tech-writer.mdc
Guide the AI to act as a Senior Technical Writer, focusing on clear and concise documentation.
NVIDIACursor rulephysicsnemo / rules
NVIDIA/physicsnemo/.cursor/rules/mod-003i-docstrings-should-include-cross-references.mdc
Docstrings should use Sphinx cross-references (:class:, :func:, :meth:) to link to other code elements and external resources for better documentation connectivity.
aischeCursor rulehwfl / rules
aische/hwfl/.cursor/rules/project-docs.mdc
Project documentation workflow — when to read and update docs
Ivolga13Cursor rulecursor-russian-toolkit / rules
Ivolga13/cursor-russian-toolkit/.cursor/rules/markdown-formatting.mdc
Markdown formatting standards for clear, consistent documentation
paulophl94Cursor rulecadence-os / rules
paulophl94/cadence-os/.cursor/rules/cadence-workflows.mdc
PM Workflows - Automated workflows for document generation
G0rg0neCursor ruleShip-of-Theseus / rules
G0rg0ne/Ship-of-Theseus/.cursor/rules/cursorrules.mdc
Core project standards and documentation workflow for Ship of Theseus
NVIDIACursor rulephysicsnemo / rules
NVIDIA/physicsnemo/.cursor/rules/mod-003e-tensor-shapes-must-use-latex-math-notation.mdc
All tensor shapes in docstrings must use LaTeX math notation like :math:`(B, C, H, W)` for proper rendering in Sphinx documentation.
leshchenko1979Cursor rulefast-mcp-telegram / rules
leshchenko1979/fast-mcp-telegram/.cursor/rules/docs-plain-language.mdc
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank)
sisimomoCursor ruleaivm / rules
sisimomo/aivm/.cursor/rules/markdown.mdc
Enforce markdownlint-cli2 rules when generating or updating documentation
paulophl94Cursor rulecadence-os / rules
paulophl94/cadence-os/.cursor/rules/product-context.mdc
Product Context - Core product knowledge for all generated documents
moclam1905Cursor ruleCocktailRecipes / android-kotlin-compose-rules
moclam1905/CocktailRecipes/.cursor/rules/android-kotlin-compose-rules/technical_design_documentation_rule.mdc
Rule: Guideline for creating a Technical Design Document for a new feature
moclam1905Cursor ruleCocktailRecipes / tool-rules
moclam1905/CocktailRecipes/.cursor/rules/tool-rules/git-commit-push-agent.mdc
This rule governs the process of committing and pushing changes to git repositories. It should be applied whenever: (1) The user indicates they want to commit or push changes, (2) The user asks about git commit conventions, (3) The user wants to update or save their work to git, or (4) Any git-related commit and push operations are requested. The rule ensures consistent commit message formatting, proper change documentation, and maintainable git history. It's particularly important for maintaining clear project history, facilitating code reviews, and ensuring proper documentation of changes. This rule helps maintain high-quality commit messages that explain both what changed and why, making it easier for both humans and AI to understand the project's evolution.
AlephantAICursor ruleAIephant-AI-Agent-Gateway / rules
AlephantAI/AIephant-AI-Agent-Gateway/.cursor/rules/docs-and-artifacts-path.mdc
alephant-ai-gateway documentation and artifact paths; agents must follow when generating docs, plans, or audits
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.