What problem does it solve? Iterating on a Godot game requires repeatedly reloading the filesystem, running scenes, reading errors, and fixing scripts. This Skill standardizes that loop through MCP tools so every change is immediately tested and errors are fixed surgically instead of rewriting whole files. ## Core Features & Use Cases - Build-Run-Fix Loop: Reload the filesystem, run a scene, read detailed errors with file and line numbers, fix, and repeat until zero errors remain. - Dock Progress Logging: Mandatory godot_log calls before and after every action so the Godot editor dock panel always shows live progress. - Error Resolution Patterns: A reference table of common GDScript errors (missing identifiers, type mismatches, cyclic references, collision layer issues) with concrete fixes, plus cascading-error diagnosis for broken autoloads. - Use Case: After generating player movement scripts, run the scene, discover an "Identifier not found" error caused by a missing autoload, register it in project.godot, reload, and verify a clean run. ## Quick Start Ask the AI to run the Godot project, check for errors with the MCP tools, and fix any issues it finds until the game runs cleanly.