Test Driven Development
SkillDev toolsUse before changing behavior or fixing a bug when a focused test can prove the change.
Then ask your AI: use the Test Driven Development skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
What this skill tells your AI
The instructions your AI receives, as published by rakuensoftware/aimee in skills/test-driven-development/SKILL.md and read by Ahel’s review.
Use this when behavior is changing and the system can express the desired result as a test.
Work in this order:
- Write or update the smallest test that proves the desired behavior.
- Run it and confirm it fails for the expected reason.
- Make the smallest implementation change that can pass the test.
- Run the focused test again.
- Refactor only after the test is green, then rerun the relevant test.
Do not treat a compile error, unrelated fixture failure, or unrun test as a valid red phase. The red phase must show the behavior gap you intend to close.
Signals
- GitHub stars
- 187
- Forks
- 69
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
test-driven-development-rakuensoftware- Source
- github.com/rakuensoftware/aimee
github.com/rakuensoftware/aimee