Cursor rules examples

przeprogramowaniCursor rule

ai-rules-builder / rules

przeprogramowani/ai-rules-builder/.cursor/rules/vitest-unit-testing.mdc

Unit testing with Vitest and React Testing Library

apacheCursor rule

nifi / rules

apache/nifi/.cursor/rules/testing-standards.mdc

Shared test coding conventions for all NiFi automated tests (framework and extensions)

Zulut30Cursor rule

dart-mobile-game-studio / rules

Zulut30/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 rule

true-skills / rules

katalon-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.

galyarderlabsReads credentialsCursor rule

galyarder-framework / rules

galyarderlabs/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 rule

chia-blockchain / rules

Chia-Network/chia-blockchain/.cursor/rules/testing-guide.mdc

Chia test harness routing — pick the right guide and harness before writing tests

No other project uses it yet

y-miyazakiCursor rule

config / rules

y-miyazaki/config/.cursor/rules/go-test.mdc

Go test authoring conventions for tests, stubs, and test pairing

asap-protocolCursor rule

asap-protocol / rules

asap-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 rule

novu / rules

novuhq/novu/.cursor/rules/safe-api-tests.mdc

NEVER run apps/api mocha tests without NODE_ENV=test — drops dev MongoDB

sipyourdrink-ltdCursor rule

bernstein / rules

sipyourdrink-ltd/bernstein/.cursor/rules/build-test.mdc

Build & test

datahub-projectCursor rule

datahub / rules

datahub-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 rule

ai-playbook / rules

linuxchata/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 rule

true-skills / rules

katalon-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 rule

true-skills / rules

katalon-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 rule

dd-trace-py / rules

DataDog/dd-trace-py/.cursor/rules/testing.mdc

Testing guidance - use run-tests skill for validation

OpnFormCursor rule

OpnForm / rules

OpnForm/OpnForm/.cursor/rules/front-end-testing.mdc

Front-end Testing Nuxt app with Vitest and Vue Test Utils

No other project uses it yet

The-OpenROAD-ProjectCursor rule

OpenSTA / rules

The-OpenROAD-Project/OpenSTA/.cursor/rules/opensta-tests.mdc

Where OpenSTA regression tests live (pvt/test vs public test/)

prassanna-ravishankarCursor rule

clearml-mcp / rules

prassanna-ravishankar/clearml-mcp/.cursor/rules/testing-philosophy.mdc

testing philosophy and behavioral testing approach

jdrbcCursor rule

podly_pure_podcasts / rules

jdrbc/podly_pure_podcasts/.cursor/rules/testing-conventions.mdc

Writing tests

dfinityCursor rule

oisy-wallet / rules

dfinity/oisy-wallet/.cursor/rules/40-testing.mdc

Frontend testing rules. Apply when creating or modifying tests.