What problem does it solve? Testing a game only inside the editor hides real-device issues with input, performance, and screen behavior. This Skill guides you through running a debug build on an actual phone, tablet, or another computer while keeping the editor's debugger, console, and profiler connected. ## Core Features & Use Cases - Capability verification: Checks the exact engine build's export templates and platform toolchain before attempting any deploy, so you never chase a target the build cannot support. - Prerequisite orchestration: Walks through script-error checks, runnable export preset configuration in export_presets.cfg, main scene validation, and device detection in the correct order. - On-device debugging: Explains how the deployed debug build connects back to the editor so Output, breakpoints, and the profiler work exactly like a local run. - Use Case: A user says "run this on my Android phone" but the Remote Deploy button is greyed out. The Skill diagnoses that the preset is not marked Runnable, the device is unauthorized in adb, and walks through fixing each gate. ## Quick Start Ask the agent to check why the Remote Deploy button is greyed out and get the game running on your connected phone.
