cursor-russian-toolkit / rules
Ivolga13/cursor-russian-toolkit/.cursor/rules/markdown-formatting.mdc
Markdown formatting standards for clear, consistent documentation
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.
Ivolga13/cursor-russian-toolkit/.cursor/rules/markdown-formatting.mdc
Markdown formatting standards for clear, consistent documentation
paulophl94/cadence-os/.cursor/rules/cadence-workflows.mdc
PM Workflows - Automated workflows for document generation
G0rg0ne/Ship-of-Theseus/.cursor/rules/cursorrules.mdc
Core project standards and documentation workflow for Ship of Theseus
canyonlabz/perfpilot-hub/.cursor/rules/project-and-coding-guidelines.mdc
PerfPilot safety, approvals, planning, branches, documentation, and delivery requirements
canyonlabz/perfpilot-hub/.cursor/rules/technology-reference-policy.mdc
PerfPilot version-aware technical documentation and protocol verification
daledesilva/obsidian_ink/.cursor/rules/preserve-sync-debug-logs.mdc
Never delete sync or debug session logs mid-investigation — preserve runtime evidence until the user is finished committing or documenting
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.
Steady17 mentions in 2 weeks
No other project uses it yet
leshchenko1979/fast-mcp-telegram/.cursor/rules/docs-plain-language.mdc
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank)
gnomatix/steering/.cursor/rules/audit-skill.mdc
Audit a SKILL document — Claude Code SKILL.md, Cursor .mdc agent skill, Kiro skill, or equivalent invocable capability with frontmatter. Runs the standard checklist plus reference-exemplar comparison plus portability/graceful-degradation audit (cross-platform support, OSS alternatives to proprietary services). Use for invocable skill files. SKIP for always-on rules (use audit-rule) or multi-step workflow documents (use audit-workflow).
gnomatix/steering/.cursor/rules/audit-workflow.mdc
Audit a WORKFLOW document — multi-step procedure, runbook, SOP, Kiro spec, Antigravity workflow, plan-mode document. Runs the standard checklist plus phase-boundary checks (are checkpoints meaningful, are approval gates correctly placed) plus portability audit. Use for multi-step procedures with phases. SKIP for always-on rules (use audit-rule) or single-pass invocable skills (use audit-skill).
thehimel/cursor-rules-and-prompts/.cursor/rules/academic/lecture-reference-linking.mdc
Guidelines for including course materials lists and inline references when writing exam answers or documentation that references course materials
sisimomo/aivm/.cursor/rules/markdown.mdc
Enforce markdownlint-cli2 rules when generating or updating documentation
paulophl94/cadence-os/.cursor/rules/product-context.mdc
Product Context - Core product knowledge for all generated documents
thehimel/cursor-rules-and-prompts/.cursor/rules/general/code-migration.mdc
Guidelines for ensuring all references are updated when moving files or directories. Covers code references, configuration files, documentation, and verification steps.
zoom/skills/.cursor/rules/zoom-platform.mdc
For Zoom Developer Platform tasks, prefer current official documentation over memory and route to the matching skill under skills/.
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
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
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.
Helicone/ai-gateway/.cursor/rules/.task-magic/plans.mdc
This rule specifies the technical details for creating Product Requirements Documents (PRDs), also known as plans, in the project's file-based planning system.
Peak-Studios/peak-agent-toolkit/.cursor/rules/peak-scripts.mdc
Use public Peak Studios documentation when modifying Peak FiveM scripts
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.