CADAM / rules
Adam-CAD/CADAM/.cursor/rules/frontend-architecture.mdc
No summary in the file. Open it to read it.
The rules real projects give Cursor's agent, from .cursor/rules.
Adam-CAD/CADAM/.cursor/rules/frontend-architecture.mdc
No summary in the file. Open it to read it.
Adam-CAD/CADAM/.cursor/rules/typescript-workflow.mdc
You can also run the npm command
robinebers/openusage/.cursor/rules/openusage-preview-launch.mdc
Always kill and relaunch the local OpenUsage dev build after app changes or when asked
melgarafael/DeskcommCRM/.cursor/rules/deskcomm-guias.mdc
Guias do assistente do DeskcommCRM — quando usar cada um
yvgude/lean-ctx/.cursor/rules/compression-safety.mdc
lean-ctx shadow-mode hooks compress file reads. If an edit tool (StrReplace, Write) reads through the hook, it sees compressed content and writes markers like [lean-ctx: omitted N lines] back to disk. This silently destroys file content. The pre-commit hook blocks commits containing [lean-ctx: omitted markers. If your commit is blocked, the file was corrupted. Fix: Always use LEANCTXDISABLED=1 when restoring files from git: NEVER use git show commit:file > file — the shell redirect writes compressed output. If a file…
vercel-labs/wterm/.cursor/rules/avoid-useeffect.mdc
Avoid useEffect in React/Next.js components
letta-ai/letta-code/.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc
../../AGENTS.md
NVIDIA/physicsnemo/.cursor/rules/mod-000a-reusable-layers-belong-in-nn.mdc
Reusable layers and building blocks should be placed in physicsnemo/nn, not physicsnemo/models. Examples include FullyConnected, attention layers, and UNetBlock.
NVIDIA/physicsnemo/.cursor/rules/mod-000b-complete-models-belong-in-models.mdc
Complete models composed of multiple layers should be placed in physicsnemo/models, not physicsnemo/nn. These are domain-specific or modality-specific models.
NVIDIA/physicsnemo/.cursor/rules/mod-001-use-physicsnemo-module-as-base-class.mdc
All model and layer classes must inherit from physicsnemo.Module (not torch.nn.Module directly) to ensure proper serialization, versioning, and registry functionality.
NVIDIA/physicsnemo/.cursor/rules/mod-002a-experimental-models-belong-in-experimental.mdc
New model classes should start in physicsnemo/experimental/nn or physicsnemo/experimental/models during development, where backward compatibility is not guaranteed.
NVIDIA/physicsnemo/.cursor/rules/mod-002b-add-deprecation-warnings-to-model.mdc
Model classes being deprecated must include deprecation warnings in both docstring and runtime, explaining why and what users should use instead, for at least 1 release cycle.
NVIDIA/physicsnemo/.cursor/rules/mod-002c-remove-deprecated-model-from-codebase.mdc
After at least 1 release cycle in pre-deprecation stage with warnings, deprecated model classes can be deleted from the codebase.
NVIDIA/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.
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.
NVIDIA/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::.
NVIDIA/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::.
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.
NVIDIA/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.
NVIDIA/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.
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.