Use Cases
When developing new features, developers use this skill to ensure every feature point is test-covered first. For example, implementing a user registration feature: write tests for email validation, password strength requirements, duplicate registration detection; watch tests fail due to missing features; write minimal code to pass tests; then refactor. This ensures every feature point is covered by tests, preventing missed edge cases and enabling regression detection.
When a bug is found, developers first write a failing test that reproduces the bug, then fix the code to make it pass. By watching the test fail (confirming the test correctly captures the bug) and then pass (confirming the fix works), this ensures: 1) the fix actually solves the problem; 2) the test permanently prevents regression. This transforms bug fixes into automated regression detection.
Skill File
Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
Strictly follows the Red-Green-Refactor cycle:
Iron Law: Production code written before a failing test? Delete it and start over.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
