tdd
Skill0 starsChanged 5 months agoMITView on GitHub
Feature veya bugfix implementasyonunda, uygulama kodu yazmadan ONCE kullan
194 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- e2b-dev/E2Btheir own version, first seen Nov 15, 2026
- backnotprop/pstacktheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
The-Vibe-CompanySkillcapture-learning-tools
Turn technical conversations, bugs, CI failures, review comments,
Also in 5 projects that use this
The-Vibe-CompanySkilldesign-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to
Also in 5 projects that use this
jaydubya818Skillfigure-it-out
Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.
Also in 61 projects that use this
jaydubya818Skillprinciple-minimize-reader-load
Apply when layers, wrappers, or hidden state make simple behavior hard to follow.
Also in 53 projects that use this
- +2 more from The-Vibe-Company
- +6 more from jaydubya818
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- mattpocock/skills★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- trpc/trpc★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- MODSetter/SurfSense★ 17ksame name
- GreyDGL/PentestGPT★ 16ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- proje/CLAUDE.mdCLAUDE.md
- adr-writerSkill
- brainstormingSkill
- brainstormSkill
- code-auditSkill
- commitSkill
- create-prSkill
- governance-evalSkill
- governance-kurSkill
- migration-checklistSkill
- security-scanSkill
- stack-loaderSkill
- systematic-debuggingSkill
- test-scaffoldSkill
- yeni-projeSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 187 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Test'ten once kod yazdiysan → sil, bastan basla.
- Distinctive: line 63
Test FAIL ediyor mu? (error degil, FAIL)
- Distinctive: line 67
Test PASS ediyorsa → mevcut davranisi test ediyorsun, test'i duzelt.
- Distinctive: line 71
Test'i gecirmek icin EN BASIT kodu yaz.
- Distinctive: line 98
Test PASS ediyor mu?
- Distinctive: line 155
Test'ten once kod yazdin
- Distinctive: line 156
Test hemen PASS etti (mevcut davranisi test ediyorsun)
“Common” is measured: kept by at least 6 in 10 of the 187 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test-Driven Development (TDD)
Temel Kural
FAILING TEST OLMADAN UYGULAMA KODU YAZILMAZ. ISTISNASI YOK.Test'ten once kod yazdiysan → sil, bastan basla.
Ne Zaman Kullanilir
Her zaman:
- Yeni feature
- Bug fix
- Refactoring
- Davranis degisikligi
Istisnalar (kullaniciya sor):
- Bir kerelik prototip
- Generate edilen kod
- Config dosyalari
Red-Green-Refactor Dongusu
RED — Failing Test Yaz
Tek bir davranisi gosteren minimal test yaz.
// IYI: Net isim, gercek davranisi test eder
test('should return 404 when user does not exist', async () => {
const res = await request(app).get('/api/v1/users/999');
expect(res.status).toBe(404);
expect(res.body.error.code).toBe('NOT_FOUND');
});// KOTU: Belirsiz isim, mock test eder
test('user test', async () => {
const mock = jest.fn().mockResolvedValue(null);
expect(mock).toHaveBeenCalled();
});Kurallar:
- Tek davranis
- Acik isim (ne test ettigini soyle)
- Gercek kod test et (mock sadece kacinilmazsa)
RED DOGRULA — Hata Verdigini Gor
npm test path/to/test.test.ts- Test FAIL ediyor mu? (error degil, FAIL)
- Hata mesaji beklenen mi?
- Feature eksik oldugu icin mi fail ediyor (typo degil)?
Test PASS ediyorsa → mevcut davranisi test ediyorsun, test'i duzelt.
GREEN — Minimal Kod Yaz
Test'i gecirmek icin EN BASIT kodu yaz.
// IYI: Yeterli kadar
async function getUserById(id: string) {
const user = await db('users').where('id', id).first();
if (!user) throw new NotFoundError('User not found');
return user;
}// KOTU: Over-engineered
async function getUserById(
id: string,
options?: { cache?: boolean; include?: string[]; transform?: (u: User) => any }
) { /* YAGNI */ }Feature ekleme, baska kodu refactor etme, test'in otesinde "iyilestirme" yapma.
GREEN DOGRULA — Gectigini Gor
npm test path/to/test.test.ts- Test PASS ediyor mu?
- Diger testler hala geciyor mu?
- Ciktida hata/uyari yok mu?
REFACTOR — Temizle
Sadece GREEN'den sonra:
- Tekrari kaldir
- Isimleri iyilestir
- Helper'lar cikar
Testler yesil kalsin. Yeni davranis EKLEME.
Tekrarla
Siradaki davranis icin yeni failing test yaz.
Bug Fix Ornegi
Bug: Bos email kabul ediliyor
RED:
test('should reject empty email with validation error', async () => {
const res = await request(app)
.post('/api/v1/auth/register')
.send({ email: '', password: 'Test1234!' });
expect(res.status).toBe(422);
expect(res.body.error.code).toBe('VALIDATION_ERROR');
});RED DOGRULA: FAIL — expected 422, got 201 ✓
GREEN:
if (!data.email?.trim()) {
throw new ValidationError('Email zorunludur');
}GREEN DOGRULA: PASS ✓
REFACTOR: Baska alanlar icin de validation gerekiyorsa cikar.
Yaygin Bahaneler
| Bahane | Gercek |
| "Test yazacak kadar basit degil" | Basit kod da kirilir. Test 30 saniye surer. |
| "Sonra test yazarim" | Hemen gecen test hicbir sey kanitlamaz. |
| "Once elle test ettim" | Elle test sistematik degil, tekrar calistirilamaz. |
| "X saatlik isi silmek israf" | Batik maliyet yanilgisi. Test edilmemis kod teknik borc. |
| "TDD beni yavaslatir" | TDD debugging'den hizli. |
Kirmizi Bayraklar — DUR ve Bastan Basla
- Test'ten once kod yazdin
- Test hemen PASS etti (mevcut davranisi test ediyorsun)
- Neden FAIL ettigini aciklayamiyorsun
- "Bir kerelik istisna" bahanesi
- "Referans olarak tutayim" (= test'ten sonra yazma)
Tumu = Kodu sil. TDD ile bastan basla.
Dogrulama Listesi
Isi tamamlandi olarak isaretlemeden once:
- Her yeni fonksiyon/metod icin test var
- Her test'in fail ettigini gordun
- Her test beklenen sebeple fail etti (feature eksik, typo degil)
- Her test icin minimal kod yazdin
- Tum testler geciyor
- Testler gercek kod kullaniyor (mock sadece kacinilmazsa)
- Edge case'ler ve hata senaryolari kapsanmis
test-scaffold ile Farki
test-scaffold: Test DOSYASI olusturma pattern'leri — naming, yapi, AAA, edge case uretimitdd: Gelistirme SURECI — once test yaz, fail gordukten sonra implement et
Birlikte kullanilirlar: TDD sureci icinde test-scaffold pattern'leri uygulanir.
Kaynak: obra/superpowers (uyarlanmis versiyon)
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.

