Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Investigate performance in [mobile game] during [repeatable scene] on [device range]. Record the target experience, build configuration, test duration, and starting conditions. Measure frame timing and relevant resource use through gameplay and scene transitions.
Distinguish isolated hitches, sustained rendering or simulation cost, loading peaks, and degradation during longer play. Use the available profiling tools to test a concrete explanation before changing code. Make a focused improvement and compare the same scenario under comparable conditions.
Recheck input response, essential visual feedback, audio, and game rules. Report measurements, the identified bottleneck, the tradeoff made, and the devices or situations that still need verification.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.
- Android — thermal throttling and sustainable workload
- Android — game frame pacing
- Godot — profiling frame, script, physics, and audio time
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original profiling template grounded in thermal, pacing, and profiler concepts. Bottlenecks and before/after measurements are to be established by the user project.