cf-tdd
SolidUse when writing new production code, adding features, implementing changes, or refactoring existing code — e.g. "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "clean up this code", "extract into a module", "simplify this function", "scaffold", "write a test", "add tests", "create a component", "implement the API", "add a route", "write a service", "create the handler". Also auto-invoke when the conversation transitions from planning/discussion to actual code writing — any time production code is about to be written, this skill MUST be loaded first. By default uses direct implementation (no new tests written). TDD is enabled when `--add-tests` is present or config `tdd: true`. This is the gate for all code writing in the project. Do NOT auto-invoke for documentation-only changes, config edits, non-code file updates, or when the user is only asking questions about code without requesting changes.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- dinhanhthi
- Repository
- dinhanhthi/coding-friend
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
tdd
Test-driven work in two modes. Default: real Test-Driven Development — red-green-refactor, one failing test at a time, used while implementing features (and by the work skill). With --debug: test-first debugging — generate all plausible root-cause hypotheses, write tests to validate each before touching production code, fix based on which tests fail, then sweep the codebase for the same pattern. Use for 'tdd', 'test-driven', 'write the test first', implementing with tests leading — and with --debug whenever the user reports a bug, unexpected behavior, or failed fix attempts and the root cause is unclear.
tdd
Write code through a disciplined, BDD-framed Test-Driven Development loop: build a behavior test list, then drive each behavior through red-green-refactor with an enforced observed-failure gate. Use when the user wants to implement, build, or write code test-first, "do TDD", follow "red-green-refactor", drive code from tests, choose the next test by the Transformation Priority Premise (TPP) or ZOMBIES ordering, or grow a feature behavior-by-behavior with tests leading. This skill writes and changes code; it does not produce a test plan document (use test-planning), review or audit existing code (use code-review), restructure existing code outside a TDD loop (use refactor), specify what a feature should do (use plan-a-feature), or find the root cause of a bug (use investigate).
tdd
Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly requested.