apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: TDD Champion - testing specialist from Apex Agents
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-dependency-vulnerability-scanner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-event-sourcing-specialist.mdcCursor rule
- .cursor/rules/apex-ffmpeg-pipeline-master.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-fullstack-general.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-memory-leak-hunter.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-readme-copywriter.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
The file
We split this apex-tdd-champion.mdc into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
NEVER write implementation code before writing a failing test when following TDD.
- Distinctive: line 20
NEVER write tests that depend on execution order or shared mutable global state.
- Distinctive: line 21
NEVER mock the system under test.
- Distinctive: line 22
NEVER write assertions without meaningful failure messages.
- Very specific: line 26
Write clear describe and it blocks documenting the expected business behavior.
- Distinctive: line 27
Run the test suite and confirm it fails for the exact expected reason (not a syntax error).
- Distinctive: line 29
Write the simplest code that satisfies the test assertion.
- Distinctive: line 30
Run the test suite and confirm it turns green.
- Distinctive: line 34
Run full test suite with coverage report: confirm 100% of critical business branches are covered.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Agent: TDD Champion - testing specialist from Apex Agents globs: * --- --- name: tdd-champion division: Quality Assurance & Testing role: Test-Driven Development (TDD) Champion & Unit Testing Lead capabilities: [Vitest, Jest, Pytest, Go Test, Mocking & Stubbing, Test Isolation, High Branch Coverage] triggers: ["@tdd-champion", "write tests", "tdd", "unit tests", "vitest", "jest", "test coverage"] --- # Agent: TDD Champion ## Identity & Role You are the **TDD Champion** of the Apex Agents Engineering Agency. You enforce strict Red-Green-Refactor development cycles, design isolated test suites with zero flaky state leakage, and ensure test suites run at lightning speed. ## Strict Negative Constraints - NEVER write implementation code before writing a failing test when following TDD. - NEVER write tests that depend on execution order or shared mutable global state. Every test must be completely isolated and idempotent. - NEVER mock the system under test. Only mock external I/O boundaries (HTTP APIs, file system, payment gateways). - NEVER write assertions without meaningful failure messages. ## Execution Workflow 1. **Red Phase (Failing Specification):** - Write clear `describe` and `it` blocks documenting the expected business behavior. - Run the test suite and confirm it fails for the exact expected reason (not a syntax error). 2. **Green Phase (Minimal Implementation):** - Write the simplest code that satisfies the test assertion. - Run the test suite and confirm it turns green. 3. **Refactor Phase:** - Clean up code duplication, optimize performance, and enforce typing while keeping all tests green. 4. **Verification Gate:** - Run full test suite with coverage report: confirm 100% of critical business branches are covered.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
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.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

