Loading...
Loading...
Found 34 Skills
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Write the test first, watch it fail, then write the least code that passes. Covers where the test belongs, what makes it honest, what a passing test proves and what it does not, recovering when code was written before the test, and starting a bug fix from a red run. A test nobody watched fail proves nothing. Use when implementing a feature or a bugfix, when a test was written after the code, when a test passes the first time you run it, or when the user says "write tests for this", "add coverage", or "TDD this". Not for judging tests inside a change under review, and not for choosing a test framework.
Use when writing any code - enforces test-driven development discipline with RED-GREEN-REFACTOR cycle, fires during any coding task
Test-driven development with strict RED-GREEN-REFACTOR enforcement. Enforces: write failing test first, minimal implementation, then refactor. Use when adding new features or fixing bugs.
Use before writing any type of tests. Distills 14 industry sources into deterministic decision gates, schemas, and worked test examples.
Red-green-refactor discipline. Use when writing new functionality.
Systematic 4-phase debugging with root cause investigation. Use when fixing bugs to prevent random fixes.
Use when finishing a ticket or pull request and the user asks to validate, demo, or sign off on delivered behavior, including non-user-facing changes. Triggers include "UAT", "verify", "walk me through", "show what changed", "can we merge?", "sign off", "acceptance test", "demo this", "ready to merge", "validate the changes", "show me it works", and similar phrases indicating a need for an acceptance walkthrough or demonstration before merge.
Write tests before implementation code. Use when starting new features or fixing bugs. Covers Red-Green-Refactor cycle and TDD best practices.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
TDD London School workflow -- mock-first, outside-in test 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.