godot-platform-mobile — Claude Code skill for Godot mobile builds

What godot-platform-mobile does

This skill tells the agent how to handle the mobile half of a Godot project. It ships rules plus ready scripts: gesture recognition, safe-area insets via DisplayServer, a heat and battery monitor, Android runtime permissions, an in-app purchase boilerplate, haptic patterns, accelerometer and gravity fusion, VRAM optimisation.

The flow is decision-first. The agent walks a tree over control scheme, orientation and renderer, then loads only the scripts that match the branch. Gestures pull in mobile_gesture_recognizer.gd; adaptive orientation pulls in orientation_layout_adaptor.gd together with the size_changed signal.

The prohibitions carry more weight than the advice. Touch must not go through InputEventMouseButton — that path is unreliable on phones, so use InputEventScreenTouch and InputEventScreenDrag. Forward+ is a bad fit for phone GPUs; pick Mobile or Compatibility. Leaving ETC2/ASTC compression off ends in VRAM exhaustion and a crash. Android permissions are never granted for free: request them with OS.request_permission() at the moment the feature is used, not on cold boot, and confirm with OS.get_granted_permissions(). Big saves on the main thread trip ANR, so push disk I/O to background threads. If your project already has its own touch layer, these rules will fight it — check that two input handlers are not running at once.