Failing Fixture Design
A good coding fixture demonstrates one missing behavior with names and values that make the expected contract obvious.
Steps
- Pick one behavior and one assertion.
- Use realistic object names from the local domain.
- Run the fixture before implementation and confirm it fails for the expected reason.
Provenance
Seeded during v1 starter-pack expansion from goal.md. Inspired by: https://github.com/obra/superpowers and https://github.com/garrytan/gstack.