Menu
Use when implementing any feature or bugfix. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when evaluating whether a proposed change fits the existing architecture. Prevents layer violations, dependency cycles, and accidental coupling.
Use when the user wants a code review instead of implementation. Prioritizes correctness bugs, behavioral regressions, missing tests, and risky assumptions.
Use when reviewing documentation for accuracy, completeness, and alignment with source code. Catches doc-code drift before it confuses readers.
Use when making changes that should be committed. Enforces atomic commits, meaningful messages, and clean history.
Use when investigating slow execution, high memory usage, or excessive token consumption. Systematic measurement before optimization.
Use when improving code structure without changing behavior. Ensures each refactoring step preserves all existing tests.
| name | tdd |
| description | Use when implementing any feature or bugfix. Enforces RED-GREEN-REFACTOR cycle with test-first approach. |
| version | 1.0.0 |
| author | Aixlarity (adapted from Hermes Agent / obra/superpowers) |
| license | Apache-2.0 |
| metadata | {"aixlarity":{"tags":["testing","tdd","development","quality"],"related_skills":["systematic-debugging","writing-plans"],"origin":"Hermes Agent test-driven-development skill"}} |
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Write code before the test? Delete it. Start over.
# Run a specific test
cargo test -p aixlarity-core test_name
# Run all tests
cargo test
# Run with output
cargo test -- --nocapture