What problem does it solve? Writing Godot 4 code without established conventions leads to slow untyped GDScript, shared-Resource bugs, broken signal connections, and scenes that are hard to maintain. This Skill provides a consistent set of patterns, pitfalls, and MCP tool workflows for day-to-day Godot development. ## Core Features & Use Cases - Standardized Script Structure: Enforces a fixed layout for GDScript files covering class_name, signals, exports, @onready caching, and static typing for compiler optimization. - Godot MCP Tool Integration: Lists concrete MCP tools for launching the editor, running projects, creating scenes, adding nodes, and reading debug output so the AI acts directly instead of explaining steps. - Pitfall Prevention: Documents the top Godot 4 mistakes, including shared Resource instances without duplicate(), Godot 3 signal syntax that silently fails, and node lookups inside _process. - Use Case: Ask the AI to create a 2D player character; it creates a CharacterBody2D scene via MCP tools, adds Sprite2D and CollisionShape2D nodes, and attaches a fully typed movement script following the standard layout. ## Quick Start Use the godot-core skill to create a 2D player character scene with a typed movement script in my Godot project.
