crit / rules
tomasz-tomczyk/crit/.cursor/rules/go.mdc
crit — go
Steady5 mentions in 2 weeks
No other project uses it yet
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.
tomasz-tomczyk/crit/.cursor/rules/go.mdc
crit — go
Steady5 mentions in 2 weeks
No other project uses it yet
sakaiproject/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
lobehub/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
vamplabAI/sgr-deep-research/.cursor/rules/workflow.mdc
Workflow rules for bug fixes, new features, and testing
colinhacks/zshy/.cursor/rules/snapshot-updates.mdc
snapshots when the new behavior is correct - Commit snapshot updates separately from code changes for easier review
tegojs/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
tegojs/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
tegojs/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
apache/ranger/.cursor/rules/ranger-checkstyle.mdc
Apache Ranger code must pass Checkstyle on Maven verify
Fullive-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-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-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
Zippland/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
MetaMask/metamask-docs/.cursor/rules/contributor-workflow.mdc
Workflow rules for contributors and reviewers covering sidebar updates, redirects, verification, and PR expectations.
specklesystems/speckle-server/.cursor/rules/frontend-core.mdc
Core frontend development patterns for Vue 3 + Nuxt 3 applications
erpc/erpc/.cursor/rules/erpc.md
review in this repo: 1. **The fallthrough is the primary path.** For any open set (methods, vendor errors, response shapes, chains), much of tomorrow's traffic through your code will
tetherto/qvac/.cursor/rules/no-remote-code-execution.mdc
Repo-wide security guardrail — agents, skills, and hooks must never fetch and execute code from an external link (curl | bash, iwr | iex, download-then-run). Applies to all QVAC pods and surfaces.
music-assistant/mobile-app/.cursor/rules/ios-swift-dev-rule.mdc
structure. - Use SwiftLint or similar tools to enforce consistent code style. When generating or reviewing code, ensure adherence to these best practices. Identify and fix any violations to maintain high
cohnen/mcp-google-ads/.cursor/rules/gaql-google-ads-query-language.mdc
Use this to write better GAQL queries
openstory-so/openstory/.cursor/rules/production-review-panel.mdc
Four-persona senior engineering panel for production-grade code analysis and refactoring
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.