ebitengine-game

1# Ebitengine game
2 
3Deliver a game that is understandable, responsive and complete at the requested
4scope. One request can include several internal build/play/refine passes. A
5scaffold, successful build or attractive screenshot alone is not a finished game.
6For a focused fix, preserve the project's design and limit the workflow to the
7affected behavior.
8 
9The bundled starter targets **Ebitengine v2.10.5 / Go 1.25+**. This is a pinned
10baseline, not a claim about the latest release. Keep an existing project's
11versions unless an upgrade is needed and authorized. Check the pinned version's
12public API before using newer or experimental APIs. References contain patterns
13to adapt; only the bundled scripts and starter are executable deliverables.
14Their checks do not validate every reference snippet.
15 
16## Delivery workflow
17 
181. **Inspect and decide.** Read repository instructions, `go.mod`, the `RunGame`
19   entrypoint and existing tests/assets. For new games, read
20   [Design and quality](references/design-and-quality.md). Establish the player's
21   goal, repeated decision, consequence, end/retry path, intended look, platform
22   and supported input. Infer reasonable defaults; ask only for missing choices
23   that materially change the product. Record a short brief and observable
24   acceptance criteria in the project.
252. **Build a representative playable slice.** Make the central interaction and
26   its feedback work with the intended controls and visual direction. Check the
27…