Goose Game ai Driven prompt
Ok, do you see any refactoring opportunity before moving on to the next test?
Remember, we are doing TDD, so we should not spend a lot of time in any of the three steps (write a test, make it pass, refactor). We should proceed step by step, with tiny steps, incrementally shaping the solution with an emergent design. So we should avoid performing speculative design, but instead follow mainly our current needs, the ones defined by our actual features and the next feature we are going to support.
---
Ok, I agree we may extract the magic number 63, but I'm not sure what would be a good name for this... I tried naming it `LAST_POSITION`.when to use it
Community prompt sourced from the open-source GitHub repo xpepper/goose-game-ai-driven (no explicit license). A "Goose Game ai Driven prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
xpepper/goose-game-ai-driven · no explicit license
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions