sipyourdrink-ltdCursor rulebernstein / rules
sipyourdrink-ltd/bernstein/.cursor/rules/documentation-duty.mdc
Documentation duty
Cursor rules examples
The rules real projects give Cursor's agent, from .cursor/rules.
Best matchesWorked for most · soon
sipyourdrink-ltdCursor rule
langwatchCursor rulebetter-agents / rules
langwatch/better-agents/.cursor/rules/docs-directory.mdc
When writing documentation for the repository
VercelCursor rulestreamdown / rules
vercel/streamdown/apps/website/.cursor/.cursor/rules/documentation.mdc
Documentation Writing Style Guide
openlitCursor ruleopenlit / rules
openlit/openlit/.cursor/rules/documentation.mdc
Standards for OpenLIT documentation, MDX structure, navigation, examples, and terminology.
NVIDIACursor ruleNeMo-Agent-Toolkit / documentation
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/categories.mdc
Guidelines for placing documentation in the correct category within the docs/source directory
NVIDIACursor ruleNeMo-Agent-Toolkit / documentation
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/latinisms.mdc
Guidelines for avoiding Latin phrases in documentation to simplify content for a global audience
NVIDIACursor ruleNeMo-Agent-Toolkit / rules
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/general.mdc
Follow these rules when creating, modifying, or generating any code, tests, documentation, or configuration files
NVIDIACursor rulephysicsnemo / rules
NVIDIA/physicsnemo/.cursor/rules/mod-003h-parameters-must-be-documented-on-single-line.mdc
All parameters must be documented with their type and default values on a single line following NumPy docstring style format.
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.
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.
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.
affaan-mCursor ruleECC / rules
affaan-m/ECC/.cursor/rules/common-agents.md
Agent orchestration: available agents, parallel execution, multi-perspective analysis
affaan-mCursor ruleECC / rules
affaan-m/ECC/.cursor/rules/common-performance.md
Performance: model selection, context management, build troubleshooting
PostHogCursor ruleposthog / rules
PostHog/posthog/.cursor/rules/django-python.mdc
Rules for writing Python services at PostHog (Python servers powered by the Django framework)
PostHogCursor ruleposthog / rules
PostHog/posthog/.cursor/rules/rust.mdc
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
VercelCursor rulechatbot / rules
vercel/chatbot/.cursor/rules/ultracite.mdc
Ultracite Rules - AI-Ready Formatter and Linter
MicrosoftCursor ruledata-formulator / rules
microsoft/data-formulator/.cursor/rules/dev-guides-first.mdc
Require reading dev-guides before development and keeping docs in sync
triggerdotdevCursor ruletrigger.dev / rules
triggerdotdev/trigger.dev/.cursor/rules/repo.mdc
understanding the structure of the monorepo
0xJackyCursor rulenginx-ui / rules
0xJacky/nginx-ui/.cursor/rules/backend.mdc
Follow consistent coding standards and formatting rules across the project to enhance clarity. ## 5. Documentation and Comments - **English Language:** All code comments and documentation should be written in English
refly-aiCursor rulerefly / rules
refly-ai/refly/.cursor/rules/00-language-priority.mdc
variable names, function names, class names, and other identifiers MUST use English words** - **ALL documentation (READMEs, API docs, inline documentation) MUST be in English** - **ALL Git commit messages MUST
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.