tdd
Test-Driven Development
Drive implementation through tests using the red-green-refactor cycle.
Adapted from Matt Pocock's TDD skill
Trigger Patterns
- "use TDD"
- "TDD this feature"
- "red-green-refactor"
- "test-driven"
- "write tests first"
Do not activate for general "write tests for X" or "add test coverage" requests. This skill is specifically for the TDD workflow where tests lead implementation.
Philosophy
Test behavior, not implementation. Every test should verify what the code does from the outside, not how it works inside. See deep-modules.md for the reasoning behind this.
More from spences10/claude-code-toolkit
terminal-optimization
Terminal setup for Claude Code. Use for Ghostty config, statusline customization, voice dictation, tmux worktrees.
17reflect
Analyze session history for learnings and persist to skills. Solves \"memory zero\" - correct once, never again.
9techdebt-finder
Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
9skill-creator
Design and create Claude Skills using progressive disclosure principles. Use when building new skills, planning skill architecture, or writing skill content.
6claude-md-maintenance
Maintain CLAUDE.md files effectively. Use when adding lessons learned, updating conventions, or restructuring project instructions.
5research
Verify sources before presenting findings. Use when asked to research links or documentation.
4