Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement touch controls for [mobile game] on [supported devices and orientations]. The player uses [left-hand movement] and [right-hand action] simultaneously. Inspect the existing input layer and map gestures into its named gameplay actions.
Track individual contacts, clear released or canceled actions, and prevent menu touches from triggering gameplay. Keep important controls inside the usable display region and allow [required customization]. Define what happens when focus is lost or the app resumes.
Verify moving while acting, reversed touch order, dragging outside a target, interruption during a held action, and return to play. Test on representative physical devices where available. Report the interaction choices, devices checked, and any unverified cases.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 — multitouch identifiers, release, and cancellation
- Godot — display safe area and VSync modes
- Android — activity lifecycle and interruptions
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original control template with supported contact, cancellation, safe-area, and lifecycle premises. Device and interruption cases still require execution.