test-driven-developmentlisted

# TDD — Red-Green-Refactor This is the general TDD loop. If you need stack-specific commands and conventions, load the matching reference file with the `Read` tool based on the project's stack — check build files (`pom.xml`/`build.gradle`, `package.json`, `pyproject.toml`/`requirements.txt`) if it's unclear: - Java/Spring Boot: [references/java.md](references/java.md) - Angular/TypeScript: [references/angular.md](references/angular.md) - React/Next.js: [references/react.md](references/react.md) - Python: [references/python.md](references/python.md) If the interface's *shape* is itself in question during "Confirm Interfaces" or REFACTOR (where a seam belongs, whether a module is doing too much or too little) — not the routine case of just naming a method — load [references/seams-and-interfaces.md](references/seams-and-interfaces.md) for the shared vocabulary. Before starting, check `.sixth-sense/learnings.jsonl` at the project root for entries relevant to the files/area you're about to touch — a documented pitfall on this exact class of bug saves rediscovering it from scratch. Skip silently if the file doesn't exist. --- ## The Iron Law **ONE test. ONE behavior. Watch it fail before writing code for it.** If you catch yourself about to write a second test before the first one has gone red-then-green, stop — that's the cycle breaking. ## Before Starting: Scope Check TDD structures *how* a behavior gets built once the design is understood — it doesn't establish the desig