Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Optimize [game scene] for [target hardware and intended experience]. Use a repeatable camera route or encounter with the actual textures, materials, effects, and sound activity. Establish frame-time and relevant memory measurements before making changes.
Identify the observed bottleneck using profiling and controlled comparisons. Consider rendering submissions, shader workload, transparency, resolution, asset preparation, and audio activity only where the evidence points. Change one meaningful factor at a time.
Preserve the readability of targets, hazards, interface text, and essential audio or complementary cues. Replay the same scene and verify the important gameplay rules. Report measurements, visual or audio tradeoffs, the configuration tested, and remaining coverage.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 — draw calls, batching, and GPU bottlenecks
- Godot — profiling frame, script, physics, and audio time
- Godot — audio bus routing and effects
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original optimization template grounded in rendering costs, profiling, and audio buses. It requests evidence and preserves readability without guaranteeing a performance gain.