Tdd Red Green Refactor
---
title: TDD Red → Green → Refactor
---
## When to use
When implementing any feature with testable behavior. AI-generated tests written after the code always have the same blind spots as the code itself , they confirm what the AI did, not what you wanted. Writing tests first inverts this.
## Promptwhen to use it
Community prompt sourced from the open-source GitHub repo dotsystemsdevs/vibe-prompt (MIT). A "Tdd Red Green Refactor" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
dotsystemsdevs/vibe-prompt · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions