VercelCursor rulewterm / rules
vercel-labs/wterm/.cursor/rules/avoid-useeffect.mdc
Avoid useEffect in React/Next.js components
Cursor rules examples
The rules real projects give Cursor's agent, from .cursor/rules.
Best matches · from page 8Worked for most · soon
VercelCursor rule
NVIDIACursor rulephysicsnemo / rules
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.
NVIDIACursor rulephysicsnemo / rules
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::.
NVIDIACursor rulephysicsnemo / rules
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::.
NVIDIACursor rulephysicsnemo / rules
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.
NVIDIACursor rulephysicsnemo / rules
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.
NVIDIACursor rulephysicsnemo / rules
NVIDIA/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 rulephysicsnemo / rules
NVIDIA/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.
SynkraAICursor ruleaiox-core / agents
SynkraAI/aiox-core/.cursor/rules/agents/analyst.mdc
AIOX agent @analyst - Business Analyst
SynkraAICursor ruleaiox-core / agents
SynkraAI/aiox-core/.cursor/rules/agents/architect.mdc
AIOX agent @architect - Architect
SynkraAICursor ruleaiox-core / agents
SynkraAI/aiox-core/.cursor/rules/agents/data-engineer.mdc
AIOX agent @data-engineer - Database Architect & Operations Engineer
SynkraAICursor ruleaiox-core / agents
SynkraAI/aiox-core/.cursor/rules/agents/devops.mdc
AIOX agent @devops - GitHub Repository Manager & DevOps Specialist
SynkraAICursor ruleaiox-core / agents
SynkraAI/aiox-core/.cursor/rules/agents/pm.mdc
AIOX agent @pm - Product Manager
SynkraAICursor ruleaiox-core / agents
SynkraAI/aiox-core/.cursor/rules/agents/squad-creator.mdc
AIOX agent @squad-creator - Squad Creator
VRSENCursor ruleOpenSwarm / rules
VRSEN/OpenSwarm/.cursor/rules/agency-swarm-workflow.mdc
AI Agent Creator Instructions for Agency Swarm Framework
Hugging FaceCursor rulenanotron / rules
huggingface/nanotron/.cursor/rules/pipeline-parallelism.mdc
input_keys` and `module_output_keys` - Be consistent with key naming across pipeline stages - Document expected tensor shapes ## Example Implementation ```python # Good PipelineBlock definition self.embed_tokens = PipelineBlock( p2p=self.p2p, module
NVIDIACursor ruleNeMo-Agent-Toolkit / rules
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/cursor-rules.mdc
Follow these rules when the user's request involves creating, modifying, organizing, or structuring Cursor rules within the project
NVIDIACursor ruleNeMo-Agent-Toolkit / documentation
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/capitalization.mdc
workflows, functions - **Exception**: When referring to specific proper names of products or features ## Technical Documentation Specific Rules ### UI Elements - **Match exact capitalization** of interface elements - **Bold and italic formatting**: Select
NVIDIACursor ruleNeMo-Agent-Toolkit / documentation
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/formatting.mdc
Format**: No special formatting - **Example**: Press Ctrl+Alt+Delete ### Text Formatting #### Guide Titles and Document References - **Format**: Italic text - **Example**: Refer to the *Quick Start Guide* #### Domain-Specific Terms - **Format
NVIDIACursor ruleNeMo-Agent-Toolkit / documentation
NVIDIA/NeMo-Agent-Toolkit/.cursor/rules/documentation/general.mdc
description: globs: **/*.md alwaysApply: false --- # General Documentation Rules Follow these rules when working with any documentation in the NeMo Agent Toolkit project. ## Referenced Documentation - **Project Documentation Structure**: [docs/source/](mdc:AgentIQ/docs/source
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.