tdd-workflow
Skill0 starsChanged 23 days agoMITView on GitHub
Enforces Test-Driven Development with Red-Green-Refactor cycle and 80%+ coverage. Activate when writing new features, fixing bugs, or refactoring.
128 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- lhbsaa/apex-unifiedtheir own version, first seen Nov 8, 2026
- ahmadvahidi/skill-atlastheir own version, first seen Nov 8, 2026
- mahsumaktas/agent-evolution-kittheir own version, first seen Nov 8, 2026
- ControllableModel/SWE-Skills-Benchtheir own version, first seen Nov 8, 2026
- LuisSambrano/antigravity-configtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use brand-discovery, configure-ecc 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.
ysyecustSkillbrand-discovery
Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).
Also in 6 projects that use this
royaluniondesign-sysSkillconfigure-ecc
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Also in 12 projects that use this
junimnjwSkillralphinho-rfc-pipeline
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
Also in 12 projects that use this
loulanyueSkillnuxt4-patterns
Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
Also in 10 projects that use this
royaluniondesign-sysSkillcontent-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
Also in 16 projects that use this
RojiosSkilldart-flutter-patterns
Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
Also in 7 projects that use this
Other versions128 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 128
- affaan-m/ECC★ 246ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- loulanyue/awesome-claude-notes★ 272same name
- ab604/claude-code-r-skills★ 202same name
- cloudnative-co/claude-code-starter-kit★ 153same name
- xenitV1/Antigravity-Workflows★ 130same name
- cohen-liel/hivemind★ 108same name
- travisjneuman/.claude★ 106same name
118 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 repository32 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- api-designSkill
- arch-constraint-guardSkill
- backend-patternsSkill
- clean-architectureSkill
- codebase-mappingSkill
- context-budgetSkill
- cqrsSkill
- ddd-architectureSkill
- debug-flowSkill
- dependency-auditSkill
- django-patternsSkill
- django-tddSkill
- event-driven-architectureSkill
- fd-codenavSkill
- fd-mapSkill
- frontend-patternSkill
- git-releaseSkill
- git-workflowSkill
- golang-patternsSkill
- hexagonal-architectureSkill
- java-patternsSkill
- layered-architectureSkill
- performance-profilingSkill
- postgres-patternsSkill
- python-patternsSkill
- refactor-guideSkill
- research-firstSkill
- rust-patternsSkill
- saga-architectureSkill
- security-scanSkill
- test-gap-detectorSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 117 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Write a test that describes the behavior you want.
- Very specific: line 60
Run it: npm test → must fail with "cannot find function" or similar.
- Distinctive: line 64
Write the minimum implementation:
- Very specific: line 73
Run it: npm test → must pass.
- Very specific: line 90
Run it: npm test → must still pass.
- Distinctive: line 94
After each Red-Green-Refactor cycle:
- Distinctive: line 109
Write unit tests for every function.
“Common” is measured: kept by at least 6 in 10 of the 117 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
TDD Workflow Skill
Tests before code. Always. Red-Green-Refactor is not a suggestion.
When to Activate
Activate when:
- Implementing any new feature
- Fixing any bug
- Refactoring existing code
Core Principles
- Tests before code — write the failing test first, then the implementation
- Minimum implementation — write the least code that makes the test pass
- Refactor after green — clean up only when tests are passing
- 80%+ coverage — non-negotiable threshold
Workflow
Red — Write a Failing Test
Write a test that describes the behavior you want. It must fail before you write any implementation.
// AAA Pattern: Arrange, Act, Assert
describe('calculateDiscount', () => {
it('should apply 10% discount for premium users', () => {
// Arrange
const user = { tier: 'premium' };
const price = 100;
// Act
const result = calculateDiscount(price, user);
// Assert
expect(result).toBe(90);
});
it('should return full price for standard users', () => {
// Arrange
const user = { tier: 'standard' };
const price = 100;
// Act
const result = calculateDiscount(price, user);
// Assert
expect(result).toBe(100);
});
});Run it: npm test → must fail with "cannot find function" or similar.
Green — Minimum Code to Pass
Write the minimum implementation:
function calculateDiscount(price: number, user: { tier: string }): number {
if (user.tier === 'premium') return price * 0.9;
return price;
}Run it: npm test → must pass.
Refactor — Clean Up While Green
Now clean up the implementation:
const DISCOUNT_RATES: Record<string, number> = {
premium: 0.10,
};
function calculateDiscount(price: number, user: { tier: string }): number {
const discountRate = DISCOUNT_RATES[user.tier] ?? 0;
return price * (1 - discountRate);
}Run it: npm test → must still pass.
Git Checkpoint
After each Red-Green-Refactor cycle:
git add -A
git commit -m "test: add calculateDiscount + implementation"Test Types
| Type | When | Tools |
| Unit | Functions, services with mocked deps | vitest, jest |
| Integration | API endpoints, database queries | supertest, vitest |
| E2E | Critical user flows | playwright, cypress |
Write unit tests for every function. Integration tests for every API route. E2E only for critical paths.
Coverage Check
npx vitest --coverage # vitest
npx jest --coverage # jestThreshold: 80% line coverage minimum. If below, write more tests before considering the work done.
Common Mistakes
- Writing tests AFTER implementation — these are not TDD tests
- Writing tests that always pass (asserting something trivially true)
- Skipping the Refactor step — leaving messy green code is not TDD
- Testing implementation details instead of behavior
- Giant tests that test multiple behaviors at once
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.

