Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Build a small [2D or 3D] game slice in the existing project using [engine]. The player should [move], collect [three objects], reach [an exit], see a clear success state, and restart. Inspect the current architecture and use its input, scene, and physics conventions.
Define the intended simulation timing and keep movement consistent across the supported rendering rates. Include collision behavior, pause, a readable HUD, and a deliberate restart flow. Use simple assets where needed and label placeholders.
Verify the complete journey in a packaged target build if the tools allow. Check repeated restart, duplicate collection, wall contact, and pausing during motion. Report the implementation, observed checks, and remaining setup.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Godot — complete first 2D game tutorial
- Godot — idle processing, physics ticks, and delta time
- Godot — overlap detection with Area2D
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original build template. Input/physics timing and overlap mechanics are supported; the packaged-build and restart checks are requested work, not results that ran.