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.
the-vibey-projectCursor rulethe-vibey-project/vibey/.cursor/rules/vibey-testing.mdc
The 100% per-layer coverage gates, running tests locally, Postgres integration tests (never mocked), property testing for rotation and no-loss gate, the chaos test, the test tree, and markers.
dotCMSCursor ruledotCMS/core/.cursor/rules/test-context.mdc
Testing with Spectator, Vitest, data-testid, integration tests. Use when writing or editing *.spec.ts, *Test.java, or test files.
BetterTypedCursor ruleBetterTyped/react-zoom-pan-pinch/.cursor/rules/testing.mdc
Testing conventions — always use yarn test
Steady7 mentions in 2 weeks
No other project uses it yet
maxgfrCursor rulemaxgfr/conforme/.cursor/rules/testing.mdc
testing
adammatthewsteinbergerCursor ruleadammatthewsteinberger/claudeloop/.cursor/rules/claudeloop-testing.mdc
Explains claudeloop's testing philosophy and pytest layout — fakes over mocks for every port, FakeClock/FakeSleeper for simulating multi-day waits without real sleeping, mandatory Hypothesis property tests for numeric/time-based invariants, per-layer coverage gates (100% for domain and application), and the documented # pragma no cover policy. Use this whenever writing or modifying any test under tests/, whenever the user asks how to test something in this codebase, mentions coverage, Hypothesis, property-based testing, or asks why a coverage gate failed. Make sure to consult this before adding a mock (this codebase uses fakes implementing real Protocols instead), before adding a numeric or time-based config field without a property test, and before adding a # pragma no cover without a stated reason — all three are enforced review expectations here, not suggestions.
apacheCursor ruleapache/nifi/.cursor/rules/system-test-troubleshooting-archive.mdc
Explains that every CI run of NiFi system tests uploads a per-test troubleshooting archive containing each cluster node's logs/ and conf/ directories, and how to download it when investigating a system test failure.
andr-caCursor ruleandr-ca/agentharness/.cursor/rules/testing.mdc
Use when writing tests, deciding on test coverage, choosing between unit/integration/E2E tests, applying TDD, or reviewing test quality — covers rigor tiers, the Red-Green-Refactor cycle, coverage requirements, and Playwright for UI testing.
appsmithorgReads credentialsCursor ruleappsmithorg/appsmith/.cursor/rules/playwright.mdc
Playwright E2E test conventions — POM design, assertions, selectors, test structure
No other project uses it yet
katalon-labsCursor rulekatalon-labs/true-skills/.cursor/rules/test-estimation.mdc
Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and triage, and rework separately, counts the countable part from platform data (case counts, automation split, historical pass and stability rates, configuration matrix), calibrates the rest against a rate the team supplies, and returns a three-point range with a confidence label instead of a single number. Splits resourcing across the manual and automated lanes and names the assumptions that would move the number most. For what to test and in what order, use test-plan; for a verdict on a cycle that has already run, use release-analyze. Written for the test lead sizing a cycle before it starts and the test manager who has to fund it.
vantage-shCursor rulevantage-sh/ec2instances.info/.cursor/rules/tests.mdc
Test rules
No other project uses it yet
luigi-dvCursor ruleluigi-dv/react-ts-vite/.cursor/rules/rtv-testing.mdc
What to test, where tests live and how to write them with Vitest and Testing Library.
clouderaCursor rulecloudera/hue/.cursor/rules/testing-rtl.mdc
Frontend testing with React Testing Library best practices.
isaac-simCursor ruleisaac-sim/IsaacSim/.cursor/rules/test_instructions.mdc
How to run Kit extension/application tests and standalone source/libraries module tests
Steady3 mentions in 2 weeks
No other project uses it yet
katalon-labsReads credentialsCursor rulekatalon-labs/true-skills/.cursor/rules/test-case-to-katalon-studio.mdc
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read them, model page elements as .rs test objects in the Object Repository instead of inline selectors, write WebUI, Mobile, or WS keyword steps in Groovy with Java interop, or wire data files, execution profiles, and GlobalVariable into a generated case. Also use to decide whether a headless katalonc run is possible at all, since Katalon Runtime Engine is a separately licensed paid runtime whose CLI requires -apiKey. Once a Studio run has finished and its report exists, hand off to upload-report. Written for the automation tester who has to land a manual case inside a Katalon Studio project rather than a code-first framework.
tounsilsCursor ruletounsils/claude-code-skills/.cursor/rules/test-gaps.mdc
Find the untested branches that matter, write tests that can actually fail, and report pass, fail, and skip counts honestly. Use when asked to add tests, write tests for this, improve coverage, find test gaps, check what is untested, or when a change needs test coverage before it ships.
JNTMTMTMCursor ruleJNTMTMTM/eIsland/.cursor/rules/test-file-location.mdc
Keep test files in dedicated test directories
rustic-aiCursor rulerustic-ai/codeprism/.cursor/rules/test-quality-validation.mdc
Validates test quality and prevents testing theater anti-patterns in Rust test files
osaurus-aiCursor ruleosaurus-ai/osaurus/.cursor/rules/testing-workflow.mdc
When to run tests — full suite only before PR submission, targeted tests during development
No other project uses it yet
przeprogramowaniCursor ruleprzeprogramowani/ai-rules-builder/.cursor/rules/vitest-unit-testing.mdc
Unit testing with Vitest and React Testing Library
apacheCursor ruleapache/nifi/.cursor/rules/testing-standards.mdc
Shared test coding conventions for all NiFi automated tests (framework and extensions)
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.
