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.
strapiCursor rulestrapi/documentation/.cursor/rules/strapi-docs-outline-checker.mdc
Run when the user asks to check structure, template compliance, outline review, heading hierarchy, or frontmatter validation on documentation content.
strapiCursor rulestrapi/documentation/.cursor/rules/strapi-docs-outline-generator.mdc
Run when the user needs to create an outline for new documentation from source material, or when the pipeline requires structure planning for a new page after routing.
strapiCursor rulestrapi/documentation/.cursor/rules/strapi-docs-outline-ux-analyzer.mdc
Run when the user asks for UX analysis, reader experience review, full outline review, or evaluation of documentation from the user's perspective.
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'.
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.
tomasz-tomczykCursor ruletomasz-tomczyk/crit/.cursor/rules/frontend-architecture.mdc
crit — frontend architecture
Steady6 mentions in 2 weeks
No other project uses it yet
tomasz-tomczykCursor ruletomasz-tomczyk/crit/.cursor/rules/frontend-js.mdc
crit — frontend js
Steady6 mentions in 2 weeks
No other project uses it yet
tomasz-tomczykCursor ruletomasz-tomczyk/crit/.cursor/rules/go.mdc
crit — go
Steady6 mentions in 2 weeks
No other project uses it yet
sakaiprojectCursor rulesakaiproject/sakai/.cursor/rules/sakai-rules.md
code contains `var`, suggest an explicit‑type version instead. - When editing Java, prefer clarity over brevity; avoid introducing language features that aren’t widely used in the repo. Review Gate
No other project uses it yet
lobehubCursor rulelobehub/lobe-chat-agents/.cursor/rules/development-workflow.mdc
Code Quality Checks - **TypeScript**: Use strict type checking - **ESLint**: Follow project linting rules - **Prettier**: Code formatting is handled automatically ### Testing Translation Changes ```bash # Test specific language pnpm run test:locale
vamplabAICursor rulevamplabAI/sgr-deep-research/.cursor/rules/workflow.mdc
Workflow rules for bug fixes, new features, and testing
colinhacksCursor rulecolinhacks/zshy/.cursor/rules/snapshot-updates.mdc
snapshots when the new behavior is correct - Commit snapshot updates separately from code changes for easier review
tegojsCursor ruletegojs/tego/.cursor/rules/code-style.md
检查 Lint 错误**: Run lint checks after refactoring. - **检查 Lint 错误**：重构后运行 lint 检查 ### Code Review Checklist / 代码审查清单 When reviewing code, check for: 审查代码时，检查： - [ ] Duplicate code blocks that could
tegojsCursor ruletegojs/tego/.cursor/rules/lint-check.md
exports that are not referenced elsewhere / 删除在其他地方未引用的导出 - Use tools or manual review to identify unused code / 使用工具或手动审查来识别未使用的代码 **Example / 示例:** ```typescript // ❌ Bad: Unused import / 不好的：未使用的导入 import { useState, useEffect, useMemo } from
tegojsCursor ruletegojs/tego/.cursor/rules/testing.md
tests locally / 本地运行测试 - [ ] Check test coverage / 检查测试覆盖率 - [ ] Ensure tests are independent / 确保测试是独立的 - [ ] Review test code quality / 审查测试代码质量 ## Resources / 资源 - **Vitest Documentation**: https://vitest.dev/ - **Playwright Documentation**: https://playwright.dev/ - **Testing Library
apacheCursor ruleapache/ranger/.cursor/rules/ranger-checkstyle.mdc
Apache Ranger code must pass Checkstyle on Maven verify
Fullive-AICursor ruleFullive-AI/Anima/.cursor/rules/Branch-And-Commit-Workflow.mdc
docs update tied to a code change - one regression test plus the related fix ## Commit quality Each commit should be: - small enough to review easily - coherent in purpose - safe
Fullive-AICursor ruleFullive-AI/Anima/.cursor/rules/Change-Scope-Control.mdc
root cause ## Disallowed scope expansion Do not expand scope just because you noticed: - old code you dislike - naming inconsistencies - possible future improvements - architectural ideas unrelated to the request - broad style
Fullive-AICursor ruleFullive-AI/Anima/.cursor/rules/English-First-Engineering-Workflow.mdc
Chinese text inside code-related images or diagrams - Keep the full development workflow in English unless you are explicitly asking for my decision or review, or providing the final summary
ZipplandCursor ruleZippland/perler-beads/.cursor/rules/reviewgate.mdc
user. State clearly: "Error managing `final_review_gate.py`: [specific error]. Cannot proceed with interactive review." and then conclude the interaction for the main task as best as you can without this interactive
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.
