agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-tdd-champion.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: TDD Champion - testing specialist from Apex Agents

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
  1. Distinctive:

    NEVER write implementation code before writing a failing test when following TDD.

    line 19
  2. Distinctive:

    NEVER write tests that depend on execution order or shared mutable global state.

    line 20
  3. Distinctive:

    NEVER mock the system under test.

    line 21
  4. Distinctive:

    NEVER write assertions without meaningful failure messages.

    line 22
  5. Very specific:

    Write clear describe and it blocks documenting the expected business behavior.

    line 26
  6. Distinctive:

    Run the test suite and confirm it fails for the exact expected reason (not a syntax error).

    line 27
  7. Distinctive:

    Write the simplest code that satisfies the test assertion.

    line 29
  8. Distinctive:

    Run the test suite and confirm it turns green.

    line 30
  9. Distinctive:

    Run full test suite with coverage report: confirm 100% of critical business branches are covered.

    line 34

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-tdd-champion.mdc
---
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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.