Loading...
Loading...
Found 147 Skills
TDD enforcement during implementation. Reads `tdd:` setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
Test-driven development using the RED-GREEN-refactor cycle. Suitable for users who want to build new features or fix bugs with TDD, mention "red-green-refactor", want to use integration testing, or ask about "test-first development".
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.
Enforces TDD (Red-Green-Refactor) for Rust development. Auto-triggers on implementation, testing, refactoring, and bug fixing tasks. Provides Rust-idiomatic testing patterns with anyhow/thiserror, cfg(test), and Arrange-Act-Assert workflow.
TDD London School workflow -- mock-first, outside-in test development
Use this whenever you encounter any bugs, test failures, or abnormal behavior, and execute it before proposing a fix
Expert in Python testing with pytest and test-driven development
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.
4-phase root cause debugging: understand bugs before fixing.
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
Orchestrate parallel debugging agents with root-cause tracing for multi-failure scenarios
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.