speelka-agent / rules
korchasa/speelka-agent/.cursor/rules/check-project.mdc
Project testing
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.
korchasa/speelka-agent/.cursor/rules/check-project.mdc
Project testing
katalon-labs/true-skills/.cursor/rules/true-platform-testing.mdc
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the 7-stage lifecycle (plan, design, manage, review, execute, analyze, maintain) to the right focused skill, and to decide what the Katalon MCP tools can and cannot do. Start here when a request names a job rather than one task, such as the whole chain from requirement to ship call, or when the asker wants orienting first, for example where do I start or which skill do I need. Routes the asker to the skill that owns their next step, whether they say manual tester, QA analyst, automation tester, SDET, QA engineer, test lead, QA lead, test manager, or QA manager.
katalon-labs/true-skills/.cursor/rules/test-reporting.mdc
Report Katalon True Platform/TestOps quality metrics to people outside QA. Use when you need to answer a stakeholder question with testing data, choose the few metrics that actually answer it, trend coverage, execution health, defect risk and stability across several releases, sprints, or iterations rather than inside one, and write the summary a manager presents upward at a steering committee, an exec review, or a quality business review. Produces a headline answer with the named specifics behind it, never a metric dump. The MCP returns current state with no history tool, so trends are built from execution dates plus snapshots this skill stores per period. For the ship or no-ship call on a single release, use release-analyze; for a pre-pipeline suite verdict, use test-review. Written for the test manager who has to present quality upward and the test lead who assembles the numbers.
aniketshukla1/sdlc-kit/.cursor/rules/50-testing-standards.mdc
Testing standards for pytest, Vitest, Playwright and Cypress tests.
Burla-Cloud/burla/.cursor/rules/no-unit-tests.mdc
Do not add unit tests
przeprogramowani/ai-rules-builder/.cursor/rules/playwright-e2e-testing.mdc
E2E testing with Playwright
asynkron/asynkron-skills/.cursor/rules/testrunner.md
Alternative .NET test runner for flaky, hanging, crashing, OOM, and stack overflow tests
tw93/Mole/.cursor/rules/mole-test-safety.mdc
Mole test safety and verification defaults
No other project uses it yet
first-fluke/fullstack-starter/.cursor/rules/test-guide.mdc
when working for testing or coverage.
Mazalucas/El-DT-Lightweight-Army/.cursor/rules/30-testing.mdc
Convenciones de testing, cobertura mínima, tipos de tests, mocks
hiromaily/go-crypto-wallet/.cursor/rules/go/go-test.mdc
Go Test Rules
jahongashtamc/hallwright/.cursor/rules/04-testing-tdd.mdc
Test-Driven Development (TDD) and Test Verification Rules
junimnjw/everything-claude-code/.cursor/rules/common-testing.md
Testing requirements: 80% coverage, TDD workflow, test types
Miyamura80/MCP-Template/.cursor/rules/tests.mdc
On how to write tests
niloykumarbarman/EVERYTHING-CLAUDE-CODE/.cursor/rules/common-testing.md
Testing requirements: 80% coverage, TDD workflow, test types
TechNickAI/python-template/.cursor/rules/pytest-what-to-test-and-mocking.mdc
When writing tests
TechNickAI/python-template/.cursor/rules/testing-standards.mdc
when writing tests
HumanSignal/label-studio/.cursor/rules/cypress_tests.mdc
Writing and updating cypress integration tests
No other project uses it yet
xu-xiang/everything-claude-code-zh/.cursor/rules/golang-testing.md
Go 测试 (Testing) 扩展通用规则
No other project uses it yet
Automattic/jetpack/.cursor/rules/js-testing.mdc
Guidelines to write JavaScript tests
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.