Loading...
Loading...
Found 106 Skills
Guide Test-Driven Development workflow (Red-Green-Refactor) for new features, bug fixes, and refactoring. Identifies test improvement opportunities and applies pytest best practices. Use when writing tests, implementing features, or following TDD methodology. **PROACTIVE ACTIVATION**: Auto-invoke when implementing features or fixing bugs in projects with test infrastructure (pytest files, tests/ directory). **DETECTION**: Check for tests/ directory, pytest.ini, pyproject.toml with pytest config, or test files. **USE CASES**: Writing production code, fixing bugs, adding features, legacy code characterization.
Test-driven development with Kent Beck's canonical 5-step workflow: Test List, Write Test, Make Pass, Refactor, Repeat. Strict vertical-slice cycles with automatic project detection. Use when the user asks to "write tests first", "use TDD", "red-green-refactor", "test-driven development", "build a feature with TDD", "fix a bug with TDD", wants test-first development for any language or framework, or mentions "tracer bullet" or "vertical slice".
Orchestrate parallel debugging agents with root-cause tracing for multi-failure scenarios
TDD enforcement during implementation. Reads `tdd:` setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.
Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests.
iOS Test-Driven Development standards. Enforces Red-Green-Refactor cycle, test pyramid (70/20/10), layer-specific testing strategies with XCTest and Swift Testing, and CI integration. Use when building or reviewing iOS apps with TDD methodology.
Use when implementing any code in recursive-mode Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first. Trigger phrases: "implement this", "add feature", "fix bug", "write a failing test", "TDD".