Vibe Coding
Guide a nontechnical builder through small observable iterations; inspect generated changes and verify a real task.
Use tests to make expected behavior explicit before committing to a nontrivial change.
---
name: knoveya-test-driven-development
description: "Use tests to make expected behavior explicit before committing to a nontrivial change. Use for matching engineering work."
---
# Test-Driven Development
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Use tests to make expected behavior explicit before committing to a nontrivial change.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
A meaningful regression test fails for the original defect.
## Example task
Reproduce a duplicate-submit bug before adding a guard.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-test-driven-development as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-test-driven-development/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Reproduce a duplicate-submit bug before adding a guard.
A meaningful regression test fails for the original defect.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.