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.
danielvm-gitCursor ruledanielvm-git/bigpowers/.cursor/rules/commit-message.mdc
Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for semantic-release / semver-consistent messaging before git commit.
anmolnagpalCursor ruleanmolnagpal/devops-skills/.cursor/rules/owasp.mdc
Security review requiring judgment about exploitability: injection and input handling, authentication and session management, authorization, secret storage and cryptography, and Agentic AI risks, against OWASP Top 10:2025 and ASVS 5.0. Use when user says 'review for security', 'is this secure', 'review this endpoint for injection', 'check for SQL injection or XSS', 'review auth/authorization', 'how are we storing secrets', 'check how we store secrets in this service', 'is this crypto correct', or when writing cryptography, session management, or AI agent code. Judges reachability and impact in this codebase; /clouddrove:appsec owns the deterministic checks a tool can answer (lockfile CVEs, missing headers, wildcard CORS).
andr-caCursor ruleandr-ca/agentharness/.cursor/rules/requirements-clarification.mdc
Use before implementing a significant feature or change when requirements are ambiguous, underspecified, or likely to have multiple reasonable interpretations, or when a requirement arrives pre-formed as an issue, audit finding, or review comment whose claim needs checking — covers verifying the premise before acting, structured discovery, one question at a time, edge-case probing, and writing a brief requirements summary before coding starts.
RagnarPitlaCursor ruleRagnarPitla/microsoft-agent-skills-private-archive/.cursor/rules/migrate-agent-to-skills.mdc
Move an existing agent - a prompt-stuffed assistant, a legacy chatbot, a pile of custom instructions, a hand-rolled Python agent - onto a portable skills-based harness without carrying its rot forward. Use when a system prompt has grown past what anyone can review, when someone wants to break a monolithic agent into skills, when moving off Power Virtual Agents or a bespoke framework, when the same behaviour has to run in GitHub Copilot, Claude Code, Cursor and Codex, or when a migration has produced skill files that nothing ever reaches for.
andr-caCursor ruleandr-ca/agentharness/.cursor/rules/port-agent-config.mdc
Use when asked to port, migrate, or add equivalent agent instructions, skills, or custom sub-agents for a different coding tool than the one already configured — e.g. \"add Cursor support from our CLAUDE.md\", \"we're switching from Cursor to Codex, port our rules\", \"make this work for Copilot too\", \"port our review subagent to Codex\". Covers both agentharness-linked projects (use the real generators, don't hand-write) and plain projects with hand-authored config (port by hand, same principles).
zama-aiCursor rulezama-ai/skills/.cursor/rules/zama-protocol-zama-solidity.mdc
Write, review, or debug confidential Solidity on Zama FHEVM — encrypted types and operations, ACL, public decryption, ERC-7984 confidential tokens, @fhevm/solidity, @openzeppelin/confidential-contracts, and Hardhat or Foundry setup. Also covers HCU cost and design of auctions, escrow, swaps and batchers. Load zama-protocol first; use zama-typescript for client code.
affaan-mCursor ruleaffaan-m/ECC/.cursor/rules/common-agents.md
Agent orchestration: available agents, parallel execution, multi-perspective analysis
Steady13 mentions in 2 weeks
17 projects use a version of this
affaan-mCursor ruleaffaan-m/ECC/.cursor/rules/common-development-workflow.md
Development workflow: plan, TDD, review, commit pipeline
Steady13 mentions in 2 weeks
19 projects use a version of this
affaan-mCursor ruleaffaan-m/ECC/.cursor/rules/common-git-workflow.md
Git workflow: conventional commits, PR process
Steady13 mentions in 2 weeks
1 project uses a version of this
affaan-mCursor ruleaffaan-m/ECC/.cursor/rules/common-security.md
Security: mandatory checks, secret management, response protocol
Steady13 mentions in 2 weeks
20 projects use a version of this
langflow-aiCursor rulelangflow-ai/langflow/.cursor/rules/docs_development.mdc
Guidelines for developing and maintaining Langflow documentation using Docusaurus, including content structure, style, and deployment processes.
1 project uses a version of this
streamlitCursor rulestreamlit/streamlit/.cursor/rules/agents.mdc
review comments | | `qa-testing-feature` | QA test features using Playwright | | `reviewing-local-changes` | Code review for quality, security, best practices, and product/API alignment | | `simplifying-local-changes` | Simplify and refine code
Steady4 mentions in 2 weeks
No other project uses it yet
streamlitCursor rulestreamlit/streamlit/.cursor/rules/overview.mdc
short doc note, or leaving the code as is. Security issues and data loss still need a real fix. This applies to review feedback too: a reviewer, human
Steady4 mentions in 2 weeks
No other project uses it yet
streamlitCursor rulestreamlit/streamlit/.cursor/rules/skills.mdc
third person** in descriptions (e.g., "Validates code changes" not "I validate code changes") - **Keep file references one level deep** from SKILL.md - **Use sentence casing** for titles and headers - Capitalize only
Steady4 mentions in 2 weeks
No other project uses it yet
streamlitCursor rulestreamlit/streamlit/.cursor/rules/specs.mdc
template 3. Create PR titled `[spec] Feature name` (keep in Draft until ready for review) ## Spec Guidelines ### Problem First, Solution Second Never start with what you want to build. Start
Steady4 mentions in 2 weeks
No other project uses it yet
streamlitCursor rulestreamlit/streamlit/.cursor/rules/typescript.mdc
Data fetching without race protection (stale response can overwrite newer data). ### Rewrite patterns (preferred code) - Derived value during render: ```tsx // ❌ Avoid // const [fullName, setFullName] = useState("") // useEffect(() => setFullName(`${firstName} ${lastName}`), [firstName
Steady4 mentions in 2 weeks
No other project uses it yet
appsmithorgCursor ruleappsmithorg/appsmith/.cursor/rules/agent-behavior.mdc
Agent workflow orchestration, task management, and core principles for all interactions
No other project uses it yet
PostHogCursor rulePostHog/posthog/.cursor/rules/django-python.mdc
Rules for writing Python services at PostHog (Python servers powered by the Django framework)
1 project uses a version of this
CopilotKitCursor ruleCopilotKit/CopilotKit/.cursor/rules/quick-reference.mdc
documentation - Use [react-ui/](mdc:packages/react-ui) for pre-built components ### Set Up Development Environment - Review [package.json](mdc:package.json) for workspace setup - Use scripts in [scripts/](mdc:scripts) - Check [utilities
Steady3 mentions in 2 weeks
No other project uses it yet
eyaltoledanoCursor ruleeyaltoledano/claude-task-master/.cursor/rules/self_improve.mdc
Guidelines for continuously improving Cursor rules based on emerging code patterns and best practices.
Coolinginterest down 70% this month
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.
