Loading...
Loading...
Found 94 Skills
Generic test writing discipline: test quality, real assertions, anti-patterns, and rationalization resistance. Use when writing tests, adding test coverage, or fixing failing tests for any language or framework. Complements language-specific skills.
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
Used when implementing any feature or fixing bugs, before writing the implementation code
Fix the findings recorded in a crate issue file one at a time, with failing test first, minimal fix second, full crate verification third, and issue-file status updates after each successful fix. Use for Rust crate issue lists that already exist and need disciplined sequential repair.
Used when implementing any feature or bug fix before writing production code
Structured TDD workflow that decomposes features into small specs and implements them one at a time through the strict red/green/refactor cycle. Use this skill whenever the user wants to build, implement, or fix something using TDD, test-driven development, or a test-first approach. Also trigger when the user says "red green refactor", "write tests first", "one test at a time", "failing test first", or asks to develop something incrementally with tests driving the design. Even if the user just says "use TDD" or "do it test-driven" alongside a feature request, this skill applies. Do NOT trigger for: running existing tests, adding tests after the fact to untested code, fixing a single failing test, or test infrastructure setup.
Test-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop that runs against the real app instead of mocks.
Use when implementing any feature or bugfix, before writing implementation code
Use Red→Green→Refactor for product behavior changes (features, bug fixes, domain/API logic, regression guards). Not for declarative toolchain config, docs, or mechanical edits. Use when the user mentions TDD, test-first, failing test, feature, bug fix, or behavior change in app code.
You MUST use this when implementing a behavior change - a feature, a bug fix, or a refactor whose contract is checkable - especially when a test could fail for a setup reason, assert the wrong boundary, pass without proving the requirement, or cross module, API, external, state, security, or visual boundaries. Not for purely mechanical edits with no observable behavior.