mondaycomCursor rulemondaycom/vibe/.cursor/rules/file-structures.mdc
Outlines file and directory structure conventions within the `@vibe/core` package (located in `packages/core/`), including top-level "src/" and component-specific organization (tests, stories, sub-components, hooks).
arxdsilvaCursor rulearxdsilva/vault/.cursor/rules/unit-tests-tdd.mdc
TDD for behavior changes; co-located tests; keep touched areas well covered
ashish7802Cursor ruleashish7802/awesome-agent-skills/.cursor/rules/playwright-e2e-suite.mdc
Enforces user-centric locators, hermetic test fixtures, and automated accessibility auditing.
EvilFreelancerCursor ruleEvilFreelancer/zaezd/.cursor/rules/workflow.mdc
BDD delivery order, Gherkin spec before tests before code, definition of done, Rules Sync
luisabwkCursor ruleluisabwk/kraken/.cursor/rules/systematic-debugging/RULE.md
Use when encountering bugs, test failures, unexpected behavior, or any technical issue before proposing fixes
sfmqrbCursor rulesfmqrb/pics-or-it-didnt-happen/.cursor/rules/pics-or-it-didnt-happen.mdc
No receipt, no claim. Never report tests passing or bugs fixed without running the check.
krutikJainCursor rulekrutikJain/android-agent-skills/.cursor/rules/android-testing-ui.mdc
Validate Android UI behavior with Compose UI tests, Espresso-style checks, screenshot assertions, and accessibility verification.
krutikJainCursor rulekrutikJain/android-agent-skills/.cursor/rules/android-testing-unit.mdc
Write fast, focused Android unit tests for reducers, use cases, repositories, and lifecycle-safe state holders.
rustic-aiCursor rulerustic-ai/codeprism/.cursor/rules/kubernetes.mdc
This rule provides comprehensive best practices for developing and maintaining Kubernetes applications and infrastructure, covering coding standards, security, performance, testing, and deployment.
driftwatch-kitCursor ruledriftwatch-kit/driftwatch/.cursor/rules/no-skipped-tests.mdc
TEASER — do not skip tests to go green. Incomplete; the full pack flags skip markers in CI.
kunalsuriCursor rulekunalsuri/ai-fication-kit/.cursor/rules/add-feature.mdc
Implement a feature using the knowledge layer — spec first, surgical diffs, tests before done, knowledge updated after.
vmandicCursor rulevmandic/searchconsole-mcp/.cursor/rules/code-style.mdc
Use when editing TypeScript under src/ or test/ in searchconsole-mcp (imports, Zod, stdio, tool handlers).
sordi-aiCursor rulesordi-ai/skill-everything/.cursor/rules/fastapi.mdc
Apply when building FastAPI endpoints, Pydantic models, or async APIs. Covers routing, dependency injection, error handling, testing, and OpenAPI hygiene.
luisabwkCursor ruleluisabwk/kraken/.cursor/rules/test-driven-development/RULE.md
Use when implementing any feature, bugfix, or code change - write tests first, watch them fail, then implement
danielvm-gitCursor ruledanielvm-git/bigpowers/.cursor/rules/respond-review.mdc
Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.
danielvm-gitCursor ruledanielvm-git/bigpowers/.cursor/rules/trace-requirement.mdc
Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITY_LATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find \"dark\" stories with no code.
canyonlabzCursor rulecanyonlabz/perfpilot-hub/.cursor/rules/jmeter-script-guardrails.mdc
JMeter script guardrails — smoke test limits, dry run first, backup protection, debug iteration caps
farukzahraCursor rulefarukzahra/agent-skills/.cursor/rules/finish-task-dev-server.mdc
Ao concluir tarefas, subir servidor dev e informar URL de teste
smg99Cursor rulesmg99/ticket-flow/.cursor/rules/ticket-handoff.mdc
Prompts the developer or agent to provide the standard Impact Area and ensures tests are included before handoff.
danielvm-gitCursor ruledanielvm-git/bigpowers/.cursor/rules/validate-fix.mdc
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says \"is this fixed?\", or before closing an investigation.