libGDX platform profiling
Finds platform-specific performance or packaging problems using the actual backend and device. It distinguishes Java heap, native memory, graphics and loading costs instead of treating all slowdown as one issue.
libgdx-profiling-platforms
See how it helpsWhen is it useful?
Use it when a desktop run succeeds but the packaged Android or other target build behaves differently.
What does it help you do?
- Records backend, device and Java/native versions for measurements.
- Separates heap, native memory, GPU and loading costs.
- Checks packaged assets and target-platform lifecycle independently.
Try asking this
Our Android shooter pauses during enemy waves but the desktop build is smooth. Record device and backend, measure allocation, native texture memory and draw cost, then inspect packaged assets. Recheck the same wave after the fix and identify any devices that remain untested.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
libGDX — profiling platforms
Use when diagnosing libGDX stalls, build failures, rendering or platform-specific behavior.
Version and project gate
Inspect Gradle wrapper and modules, libGDX/backend versions, Java toolchain, ApplicationListener/Game/Screen structure, AssetManager ownership, viewport policy, native libraries and supported desktop/mobile/web targets. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Capture backend, device, Java/native versions and representative route. Separate heap, native memory, GPU and asset-loading cost. Check release packaging and path case sensitivity independently of IDE runs. Adapt only the relevant Gradle backend and retain existing build conventions.
Deliver
A measured issue/fix record and target-specific build/run instructions. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A desktop backend success does not establish Android lifecycle or HTML compatibility.
Acceptance scenario
Run from packaged assets, repeat screen transitions and pause/resume on the actual target; identify any unavailable platform checks. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Keiko. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md