test-driven-development
Code changes backed by tests that fail first.
What it does
Guides code changes through failing tests, minimal implementations, and refactoring so new behavior and bug fixes have executable proof.
When to use it
Use when implementing logic, fixing bugs, modifying behavior, or adding edge case handling; exclude configuration, documentation, and static changes without behavioral impact.
How to use it
It changes how the agent implements and fixes project code by requiring a failing test before implementation and verification with the repository's own test commands.
What you provide
- An existing project
Uses
Good to know
- starts 1 helper agents
What you need · 1
Required for the browser-specific runtime verification workflow, which inspects the DOM, console, network, performance, and screenshots; not needed for non-browser changes.
Access · 0
No additional actions listed.