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.
Zulut30Cursor ruleZulut30/dart-mobile-game-studio/.cursor/rules/dart-flutter-testing.mdc
Testing & build rules for Dart/Flutter games — unit-test the pure model with dart test, widget/golden/Patrol tests, honest analyze/build reporting.
katalon-labsCursor rulekatalon-labs/true-skills/.cursor/rules/release-analyze.mdc
Analyze Katalon True Platform/TestOps release readiness from testing quality data. Use when you need to use Katalon MCP metrics and results to assess whether a release, sprint, iteration, version, test plan, suite, or repository is ready to ship; summarize requirement coverage, execution health, defect risk, test stability, configuration coverage, release blockers, quality gaps, and produce a Ready / Ready with risk / Not ready recommendation. Written for the test manager who owns the ship call and the test lead who has to defend it.
edhoferdianCursor ruleedhoferdian/EEF/.cursor/rules/desktop-e2e-edho-ferdian.mdc
End-to-end tests for Windows desktop apps (WPF, WinForms, Win32, Qt) with pywinauto over UI Automation. Use for \"test aplikasi desktop\", \"pywinauto\", \"WPF/WinForms/Qt test\", \"UI Automation\", \"test .exe ini\", or a flaky desktop GUI suite.
galyarderlabsReads credentialsCursor rulegalyarderlabs/galyarder-framework/.cursor/rules/e2e-runner.mdc
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
Chia-NetworkCursor ruleChia-Network/chia-blockchain/.cursor/rules/testing-guide.mdc
Chia test harness routing — pick the right guide and harness before writing tests
Steady5 mentions in 2 weeks
No other project uses it yet
y-miyazakiCursor ruley-miyazaki/config/.cursor/rules/go-test.mdc
Go test authoring conventions for tests, stubs, and test pairing
asap-protocolCursor ruleasap-protocol/asap-protocol/.cursor/rules/testing-standards.mdc
Testing standards for pytest, fixtures, async patterns, and test organization. Apply when writing or reviewing tests.
novuhqReads credentialsCursor rulenovuhq/novu/.cursor/rules/safe-api-tests.mdc
NEVER run apps/api mocha tests without NODE_ENV=test — drops dev MongoDB
sipyourdrink-ltdCursor rulesipyourdrink-ltd/bernstein/.cursor/rules/build-test.mdc
Build & test
Surging3 mentions in 2 weeks
1 project uses a version of this
datahub-projectCursor ruledatahub-project/datahub/.cursor/rules/test-review.mdc
DataHub test review — use when asked to review, check, validate, or audit smoke tests
No other project uses it yet
linuxchataCursor rulelinuxchata/ai-playbook/.cursor/rules/csharp-testing-standards.mdc
Defines the testing standards, patterns, and conventions for all C# unit and integration test projects. Rules cover test framework usage, naming, structure, mocking, assertions, and parameterization. Apply these rules uniformly across all test projects.
katalon-labsCursor rulekatalon-labs/true-skills/.cursor/rules/create-test-cases.mdc
Create, update, organize, and link Katalon True Platform/TestOps manual test cases from a synced requirement key such as CEL-6, a read requirement, or free-text product behavior. Use when you need to analyze requirements, design manual test cases using ISTQB techniques as a reference, check existing Katalon coverage, avoid duplicate test cases, import only missing cases, update or link existing cases, or create/reuse a test suite for newly designed cases. For full requirement-to-execution workflows, combine with or defer to true-platform-testing. Written for the manual tester who has a written requirement in hand and no cases for it yet.
katalon-labsCursor rulekatalon-labs/true-skills/.cursor/rules/analyze-failures.mdc
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create ALM-linked defects for real product bugs. This is failure diagnosis and defect filing; for the overall ship/no-ship release call use release-analyze, and for repairing the tests themselves use test-maintenance. Written for the manual tester and the automation tester looking at a red run and needing to know whether the application broke or the test did.
DataDogCursor ruleDataDog/dd-trace-py/.cursor/rules/testing.mdc
Testing guidance - use run-tests skill for validation
OpnFormCursor ruleOpnForm/OpnForm/.cursor/rules/front-end-testing.mdc
Front-end Testing Nuxt app with Vitest and Vue Test Utils
Steady4 mentions in 2 weeks
No other project uses it yet
The-OpenROAD-ProjectCursor ruleThe-OpenROAD-Project/OpenSTA/.cursor/rules/opensta-tests.mdc
Where OpenSTA regression tests live (pvt/test vs public test/)
prassanna-ravishankarCursor ruleprassanna-ravishankar/clearml-mcp/.cursor/rules/testing-philosophy.mdc
testing philosophy and behavioral testing approach
autonomous-aiCursor ruleautonomous-ai/autonomous-os/.cursor/rules/testing.mdc
Testing conventions
jdrbcCursor rulejdrbc/podly_pure_podcasts/.cursor/rules/testing-conventions.mdc
Writing tests
dfinityCursor ruledfinity/oisy-wallet/.cursor/rules/40-testing.mdc
Frontend testing rules. Apply when creating or modifying tests.
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.
