Cursor rules examples

Giskard-AICursor rule

giskard-oss / rules

Giskard-AI/giskard-oss/.cursor/rules/python.mdc

Python conventions for the giskard workspace (3.12+, Pydantic v2, async, testing).

No other project uses it yet

xu-xiangCursor rule

everything-claude-code-zh / rules

xu-xiang/everything-claude-code-zh/.cursor/rules/python-testing.md

扩展通用规则的 Python 测试 (Python testing extending common rules)

scaleapiCursor rule

scale-agentex-python / rules

scaleapi/scale-agentex-python/.cursor/rules/50_tests_and_mocking.mdc

Testing workflow and mock server details

reown-comCursor rule

appkit / rules

reown-com/appkit/.cursor/rules/appkit-apps.mdc

Focused rules for working in apps (dev, testing, wiring AppKit into apps)

No other project uses it yet

dafthunk-comCursor rule

dafthunk / rules

dafthunk-com/dafthunk/.cursor/rules/04-code-implementation-guidelines.mdc

Coding standards, naming, testing & style rules

SiriusScanCursor rule

Sirius / rules

SiriusScan/Sirius/.cursor/rules/playwright-testing.mdc

Cursor rules for using Playwright MCP for browser testing and validation

NVIDIACursor rule

Personal-AI-Router / rules

NVIDIA/Personal-AI-Router/.cursor/rules/test-type-discipline.mdc

Type-safe modular test patterns and isolation requirements

prestCursor rule

prest / rules

prest/prest/.cursor/rules/adapter-unit-tests.mdc

Postgres adapter unit tests are sqlmock-only; no real DB or sqlx.Connect

No other project uses it yet

yavdaanalyticsCursor rule

traceback / rules

yavdaanalytics/traceback/.cursor/rules/testing-files.mdc

Test file layout and conventions

SalesforceCommerceCloudCursor rule

pwa-kit / testing

SalesforceCommerceCloud/pwa-kit/.cursor/rules/testing/unit-tests-generic.mdc

USE WHEN writing unit tests for components in template packages

JasonBoyCursor rule

msw-mcp / rules

JasonBoy/msw-mcp/.cursor/rules/testing.mdc

Add Vitest tests when changing behavior in this monorepo

JustineDevsDeletes or force-pushesCursor rule

Collection / rules

JustineDevs/Collection/.cursor/rules/production.mdc

The standard way for production teams to connect frontend and backend branches and ensure integration before merging to main is to use temporary integration or "test" branches for local verification, automated testing, and code review.

laragenticCursor rule

agents / rules

laragentic/agents/.cursor/rules/testing.mdc

Testing conventions and patterns for the Laragentic package

Ame-AlCursor rule

ame / rules

Ame-Al/ame/.cursor/rules/sim-testing.mdc

Testing patterns with Vitest and @sim/testing

oniharnantyoCursor rule

go-ai-ready-boilerplate / rules

oniharnantyo/go-ai-ready-boilerplate/.cursor/rules/04-testing.mdc

Testing conventions and coverage expectations

y-miyazakiDeletes or force-pushesCursor rule

config / rules

y-miyazaki/config/.cursor/rules/bats.mdc

Bats Test Suites Instructions

coin-orCursor rule

pulp / rules

coin-or/pulp/.cursor/rules/verify-after-changes.mdc

Run unit tests, ty, and ruff checks after every code change

No other project uses it yet

jumpstarter-devCursor rule

jumpstarter / rules

jumpstarter-dev/jumpstarter/.cursor/rules/e2e-doc-sync.mdc

keep e2e README synchronized with e2e tests and runners

DataDogCursor rule

dd-trace-py / rules

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

IAST (Interactive Application Security Testing) - How it works and development guidelines

ReefJediCursor rule

coding-agent-prompts / rules

ReefJedi/coding-agent-prompts/.cursor/rules/debugger.mdc

Root-cause debugger. Use when a test fails, an error or stack trace appears, or behavior is wrong. Reproduces, isolates with evidence, applies the minimal fix plus a regression test.