zaezd / rules
EvilFreelancer/zaezd/.cursor/rules/testing.mdc
Vitest conventions and the mandatory unit-test set
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.
EvilFreelancer/zaezd/.cursor/rules/testing.mdc
Vitest conventions and the mandatory unit-test set
iharhl/embedded-agent-skills/.cursor/rules/c-conventions.mdc
Opinionated C style for firmware sources and host tests
saroj990/dockAI/.cursor/rules/github-issues.mdc
Draft GitHub issues into issues/ with standard sections and test cases
dotCMS/core/.cursor/rules/e2e-rules.mdc
Playwright E2E tests for the dotCMS admin UI. Use when editing specs, page objects or helpers under core-web/apps/dotcms-ui-e2e.
cbtw-apac/qdrant-loader/.cursor/rules/qa.mdc
Guide the AI to act as a Senior QA Engineer, focusing on test strategies and quality assurance.
saharmor/simulatedev/.cursor/rules/running_backend.mdc
Every time Cursor is trying to run the backend or test it, i.e. needing port 8000
Luxvil/ai-coding-rules/.cursor/rules/30-testing.mdc
USE WHEN: adding or changing behavior. Test-first loop.
RagnarPitla/microsoft-agent-skills-private-archive/.cursor/rules/evaluate-agent-quality.mdc
Establish whether an agent actually works, and whether it still works, using a recorded eval set rather than ad hoc chats. Use when an agent is about to ship and the only testing was somebody typing a few questions into the test pane, when an agent that used to answer correctly now does not and nobody can say when it broke, when a knowledge source or model version changed and you need to know what it affected, when a stakeholder asks how accurate it is and there is no number to give them, when you cannot decide what \"correct\" even means for a generative answer, or when the agent works for the builder and fails for a user with different permissions. For a one-off read of a single agent's configuration, review-copilot-studio-agent is the better fit; this one is about measurement over time.
golid-ai/golid/.cursor/rules/write-tests-frontend-workflow.mdc
Frontend test workflow — coverage thresholds, sync discipline, pre-push checklist
bybren-llc/safe-agentic-workflow/.cursor/rules/15-deployment.mdc
Deployment procedures: pre-deploy validation, post-deploy smoke tests, Coolify, Docker, rollback procedures.
allthingslinux/tux/.cursor/rules/testing/async.mdc
Async testing patterns, async fixtures, async test execution, and asyncio testing for Tux
pr-pm/prpm/.cursor/rules/self-improve-cursor.mdc
Automatically search and install PRPM packages when working on infrastructure, testing, deployment, or framework-specific tasks
NVIDIA/physicsnemo/.cursor/rules/mod-008b-model-missing-non-regression-test-with-reference-data.mdc
Every model must have non-regression tests comparing outputs against reference data saved in .pth files, using realistic tensor shapes and pytest parameterization.
brianwestphal/glassbox/.cursor/rules/hotsheet-instructions.mdc
Hot Sheet — ticket-driven work, testing, and requirements-doc conventions
rustic-ai/codeprism/.cursor/rules/tdd-workflow-planning.mdc
Enforces proper TDD workflow planning to prevent scope limitation and incomplete test coverage
ModelEngine-Group/nexent/.cursor/rules/test_asset_rules.mdc
Formal Nexent test-e2e feature catalog, D1-D5 case-local scripts and execution bindings, generated views, runtime, migration, and Mock profiles
vinicq/falsegreen-skill/.cursor/rules/falsegreen-skill.mdc
falsegreen-skill — false-positive test detection
yavdaanalytics/traceback/.cursor/rules/testing.mdc
Strict testing contract — real adapters in integration/e2e, adversarial fixtures
Ratimon/openquok-monorepo/.cursor/rules/backend-api-layers.mdc
Backend API layer flow — routes → controller/data/errors/utils → service → repository; add e2e tests per feature
danielvm-git/bigpowers/.cursor/rules/kickoff-branch.mdc
Create an isolated Git worktree/branch or Jujutsu workspace, then verify a clean test baseline before code. Use when starting a feature or task.
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.