implement-tdd
Skill0 starsChanged 5 months agoMITView on GitHub
Test-driven development with red-green-refactor vertical slices for Flutter/Dart
2 other projects use a version of this.
Adopted by
Most recently taken up by
- pierrebelin/claude-code-toolkittheir own version, first seen Oct 21, 2026
- oopsla5xx/oops-skillstheir own version, first seen Aug 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- pierrebelin/claude-code-toolkit★ 7same name
- oopsla5xx/oops-skills★ 4same name
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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/accessibility.mdcCursor rule
- .cursor/rules/api-integration.mdcCursor rule
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/dart-style.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/flutter-ui.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/state-management.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- doubt-reviewSkill
- fix-dependenciesSkill
- flutter-componentSkill
- flutter-implementSkill
- generate-mocksSkill
- grind-until-greenSkill
- monitor-terminalSkill
- plan-featureSkill
- repo-navigatorSkill
- review-codeSkill
- save-contextSkill
- suggest-ruleSkill
- write-commitSkill
- write-readmeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Follow .cursor/rules/testing.mdc for required coverage.
- Distinctive: line 21
Do not write all tests then all implementation.
- Very specific: line 32
Read context/ and docs/DECISIONS.md for domain vocabulary and ADRs.
- Distinctive: line 52
Only after GREEN. Extract duplication.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
Test-Driven Development
Follow .cursor/rules/testing.mdc for required coverage. All new/changed code needs tests.
Philosophy
Tests verify behavior through public interfaces, not implementation details.
- Good: "ViewModel shows error when repository returns network failure"
- Bad: testing private methods, mocking internal collaborators, asserting private fields
See tests.md for Flutter/Dart examples and mocking.md for fake vs Mockito guidance.
Anti-pattern: horizontal slices
Do not write all tests then all implementation.
WRONG: RED test1..5 → GREEN impl1..5
RIGHT: RED test1 → GREEN impl1 → RED test2 → GREEN impl2 → ...Workflow
1. Planning
Read context/ and docs/DECISIONS.md for domain vocabulary and ADRs.
Before code:
- Confirm public interfaces and behaviors to test (prioritize with user if unclear)
- List behaviors — not implementation steps
- Get user approval on the plan when scope is large
2. Tracer bullet
RED: one test, one behavior → fails
GREEN: minimal code → passes3. Incremental loop
One test at a time. Only enough code to pass the current test. No speculative features.
4. Refactor
Only after GREEN. Extract duplication; run tests after each refactor step. Never refactor while RED.
Per-cycle checklist
[ ] Test describes observable behavior
[ ] Test uses public API only
[ ] Test would survive internal refactor
[ ] Code is minimal for this test
[ ] Matching test type from testing.mdc table (unit / widget / golden)Flutter specifics
| Layer | TDD entry point |
| Repository | Unit test with Mockito dio/Supabase client |
| ViewModel | Unit test with fake repository |
| Widget / screen | Widget test; golden for design-system |
| Critical flow | integration_test after unit/widget green |
Chain grind-until-green when the slice is done.
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.