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.
thehimelCursor rulethehimel/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
sisimomoCursor rulesisimomo/aivm/.cursor/rules/markdown.mdc
Enforce markdownlint-cli2 rules when generating or updating documentation
paulophl94Cursor rulepaulophl94/cadence-os/.cursor/rules/product-context.mdc
Product Context - Core product knowledge for all generated documents
thehimelCursor rulethehimel/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.
zoomCursor rulezoom/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/.
strapiCursor rulestrapi/documentation/.cursor/rules/strapi-docs-style-checker.mdc
Run when the user asks for a style check, style review, 12 Rules compliance check, prose quality review, or writing style audit on documentation content.
AlephantAICursor ruleAlephantAI/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
moclam1905Cursor rulemoclam1905/CocktailRecipes/.cursor/rules/android-kotlin-compose-rules/technical_design_documentation_rule.mdc
Rule: Guideline for creating a Technical Design Document for a new feature
moclam1905Cursor rulemoclam1905/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.
HeliconeCursor ruleHelicone/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-StudiosCursor rulePeak-Studios/peak-agent-toolkit/.cursor/rules/peak-scripts.mdc
Use public Peak Studios documentation when modifying Peak FiveM scripts
yavdaanalyticsCursor ruleyavdaanalytics/traceback/.cursor/rules/documentation.mdc
Documentation layering — where to put README vs SETUP vs docs/ content
simtlixCursor rulesimtlix/simfinity.js/.cursor/rules/simfinity-auth-module.mdc
Documents the authorization subsystem -- Envelop plugin, permission maps, rule helpers, and policy expressions
strapiCursor rulestrapi/documentation/.cursor/rules/strapi-docs-router.mdc
Run when the user provides a spec, user story, ticket, PR, or any source material and asks where or how to update documentation. Also run when user says 'route this', 'where does this go', or 'how should I update docs'.
dazebCursor ruledazeb/coolify-mcp-enhanced/.cursor/rules/801-feature-workflow.mdc
FOLLOW feature development workflow WHEN implementing new features TO ensure consistent, tested, and documented changes
karthikrshetCursor rulekarthikrshet/ClaudeMark/.cursor/rules/clean-user-facing-text.mdc
Enforce invisible Unicode and steganography hygiene on user-facing text, manuscripts, and documentation
FalseFoundationCursor ruleFalseFoundation/taskset/.cursor/rules/taskset-standards.mdc
Apply Taskset repository architecture, storage, testing, documentation, and release standards
moclam1905Cursor rulemoclam1905/CocktailRecipes/.cursor/rules/android-kotlin-compose-rules/project_overview_template.mdc
Rule: Project architecture overview document – Android Kotlin with Jetpack Compose
Prorise-coolCursor ruleProrise-cool/claude-code-plugins/.cursor/rules/official-docs.mdc
Consult official documentation before making changes to frameworks, libraries, or platform features
adobeCursor ruleadobe/spectrum-web-components/.cursor/rules/memory-agnostic-lessons.mdc
Accumulated lessons for agents working in this repository, covering path depths, module format, repository layout, the gen2 styling API prefix, generated build output, Storybook tag conventions, and documentation style.
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.
