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.
lilishopCursor rulelilishop/lilishop/.cursor/rules/03-development-guidelines.mdc
Write unit tests for critical business logic 2. Ensure API endpoints are properly documented 3. Test both success and error scenarios
No other project uses it yet
johnlindquistCursor rulejohnlindquist/kit/.cursor/rules/derived-cursor-rules.mdc
AI rules derived by SpecStory from the project AI interaction history
No other project uses it yet
groupultraCursor rulegroupultra/telegram-search/.cursor/rules/core.mdc
safety and portability. - Reserve raw SQL for performance-critical paths and keep them well-documented. - When adding migrations: - Update TypeScript schemas/models first. - Use `drizzle-kit` to generate SQL migrations
t3-ossCursor rulet3-oss/t3-env/.cursor/rules/general.mdc
achieve strong and generic typing for your chosen API? If not, reconsider. - Create clearly documented changesets for your introduced changes using `bun changeset`. ## Coding Standards ### Naming Conventions - Variables, functions, methods
Steady4 mentions in 2 weeks
No other project uses it yet
OpnFormCursor ruleOpnForm/OpnForm/.cursor/rules/formula-engine.mdc
Formula engine for computed variables - architecture, implementation, and extension guide. Use when working with formulas, computed variables, or extending formula functions.
No other project uses it yet
haydenbleaselCursor rulehaydenbleasel/kibo/.cursor/rules/ultracite.mdc
Ultracite Rules
1 project uses a version of this
grafanaCursor rulegrafana/oncall/.cursor/rules/planit-mode.mdc
A structured approach to task planning and execution for PlanIt tasks
leaperoneCursor ruleleaperone/MultiPost-Extension/.cursor/rules/chrome-extension.mdc
Structure files logically: popup, background, content scripts, utils - Implement proper error handling and logging - Document code with JSDoc comments Architecture and Best Practices - Strictly follow Manifest V3 specifications - Divide responsibilities
No other project uses it yet
wp-graphqlCursor rulewp-graphql/wp-graphql/.cursor/rules/README.md
behavior in `wpgraphql.mdc`. ## Learn More For more information about Cursor rules, visit the [Cursor documentation](https://docs.cursor.com/context/rules-for-ai). For information about the monorepo structure, see [docs/ARCHITECTURE.md](../../docs/ARCHITECTURE.md) in the repository
No other project uses it yet
DataDogCursor ruleDataDog/datadog-agent/.cursor/rules/agent_corecheck.mdc
This rule serves for development of agent core checks.
Steady3 mentions in 2 weeks
No other project uses it yet
DataDogCursor ruleDataDog/datadog-agent/.cursor/rules/e2e_tests.mdc
Guidelines for working with E2E tests in the datadog-agent repository
Steady3 mentions in 2 weeks
No other project uses it yet
DataDogCursor ruleDataDog/datadog-agent/.cursor/rules/system_probe_modules.mdc
This rule serves for development of new system-probe modules that use eBPF, and need to send data to the backend
Steady3 mentions in 2 weeks
No other project uses it yet
superagent-aiCursor rulesuperagent-ai/grok-cli/.cursor/rules/tools-and-agent.mdc
Guidelines for the agent system and tool implementations
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-003a-missing-or-incomplete-docstring.mdc
Every model/layer requires comprehensive docstrings following NumPy style with Sphinx RST formatting, including all sub-rules MOD-003b through MOD-003k.
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-003c-missing-required-class-docstring-sections.mdc
Class docstrings must contain three mandatory sections - Parameters, Forward, and Outputs. Optional sections include Notes, Examples, ..important::, and ..code-block::.
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-003d-missing-required-method-docstring-sections.mdc
All methods must have docstrings with at least Parameters and Returns sections. Optional sections include Notes, Examples, ..important::, and ..code-block::.
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-003f-callback-functions-must-have-code-block-specification.mdc
Callback function parameters must include a ..code-block:: specification showing the required signature and return type, placed outside Parameters/Forward/Outputs sections.
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-003g-inline-code-must-use-double-backticks.mdc
Inline code in docstrings must be formatted with double backticks ``code``, not single backticks, as single backticks don't render properly in Sphinx.
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-003j-docstrings-should-include-examples-section.mdc
Docstrings should include an Examples section with executable code demonstrating usage, as these are automatically tested by CI for correctness.
NVIDIACursor ruleNVIDIA/physicsnemo/.cursor/rules/mod-006-invalid-or-missing-jaxtyping-tensor-annotations.mdc
All tensor arguments in model methods must have jaxtyping type annotations with shape specifications (e.g. Float[torch.Tensor, "b c h w"]) for runtime-checkable shape information.
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.
