factorylog / rules
flaviocopes/factorylog/.cursor/rules/restart-app-after-change.mdc
Rebuild Work Tracebook, verify changes in the test VM, then restart the local app
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.
flaviocopes/factorylog/.cursor/rules/restart-app-after-change.mdc
Rebuild Work Tracebook, verify changes in the test VM, then restart the local app
roboflow/inference/.cursor/rules/pr-description.mdc
Draft GitHub PR descriptions in Roboflow format (Linear link, testing, checklist). Invoke with @pr-description — not applied automatically.
Steady3 mentions in 2 weeks
No other project uses it yet
galyarderlabs/galyarder-framework/.cursor/rules/systematic-debugging.mdc
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
selfxyz/self/.cursor/rules/test-memory-optimization.mdc
Critical rules for avoiding out-of-memory issues in tests, specifically preventing nested require() calls that cause pipeline failures
zen-mcp/browser/.cursor/rules/10-python.mdc
Python conventions for browser-mcp runtime and tests
rlaope/nen/.cursor/rules/nen-transmuter.mdc
Behavior-preserving refactoring under characterization tests, plus severity-rated code review. Use when the user says \"refactor\", \"clean up\", \"tech debt\", \"code review\", \"extract\", \"rename\", \"restructure\", \"this file is a mess\", or \"impossible to modify\"; when every small change breaks something unrelated; when cleanup has to land before the next feature has anywhere to go; when code is called hard to change, scary to touch, or too tangled to test; when requirements shifted and the current shape fights the new feature; when a PR needs review for structure and maintainability; or when every small change keeps ballooning because everything touches everything.
Cadasto/openehr-assistant-mcp/.cursor/rules/docker-workflow.mdc
Run PHP, Composer, tests, and static analysis only via Docker in this project
millionco/expect/.cursor/rules/expect-testing.mdc
Use when testing, verifying, validating, or QA-ing code changes against a live browser. Also when expect-cli fails or needs debugging.
Steady27 mentions in 2 weeks
No other project uses it yet
NVIDIA/physicsnemo/.cursor/rules/mod-008c-model-missing-checkpoint-loading-test.mdc
Every model must have tests that load from checkpoint files (.mdlus), verify attributes, and compare outputs against reference data to ensure serialization works correctly.
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.