Loading...
Loading...
Found 131 Skills
Use when implementing any feature or bugfix, before writing implementation code
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.
Comprehensive TDD patterns and practices for all programming languages, eliminating redundant testing guidance per agent.
Red-green-refactor discipline. Use when writing new functionality.
Write tests before implementation code. Use when starting new features or fixing bugs. Covers Red-Green-Refactor cycle and TDD best practices.
RED-GREEN-REFACTOR cycle with strict phase gates. Write failing test first, implement minimum code to pass, then refactor while keeping tests green. Use when implementing new features, fixing bugs with test-first approach, improving test coverage, or when user mentions TDD. Use for "TDD", "test first", "red green refactor", "write tests", or "implement with tests". Do NOT use for debugging existing failures (use systematic-debugging) or for refactoring without new tests (use systematic-refactoring).
Test-Driven Development enforces the RED-GREEN-REFACTOR discipline on every code change an agent produces.
Enforce Test-Driven Development (TDD) workflow for all code changes. Apply PROACTIVELY by default using Red-Green-Refactor cycles for features, bug fixes, and refactoring.
Internal skill. Use cc10x-router for all development tasks.
Used when implementing any feature or fixing bugs, before writing the implementation code
Use when writing new functions, adding features, fixing bugs, or refactoring by applying TDD principles - write failing tests before implementation code, make them pass, then refactor.
TDD: enforce RED-GREEN-REFACTOR, tests before code.