What problem does it solve? Writing GDScript that compiles cleanly and integrates with Summer Engine's MCP scene tools requires knowing Godot 4.x conventions and avoiding subtle pitfalls like calling Object introspection methods on script-class references or assigning LabelSettings to Label3D nodes. ## Core Features & Use Cases - Idiomatic GDScript conventions: Enforces type hints, signal definitions, @export properties, @onready usage, and correct lifecycle method selection (_ready, _process, _physics_process). - Anti-pattern detection: Documents parse-time and runtime traps such as has_static_method on preloaded script references, $Path on optional nodes, and LabelSettings misuse on Label3D. - MCP integration guidance: Explains how scripts attach via summer_set_prop, signals connect via summer_connect_signal, and input actions bind via summer_input_map_bind. - Use Case: When building a character controller, use this Skill to write a typed movement script with exported speed values, a health signal system, and _physics_process-based move_and_slide logic that works with MCP scene operations. ## Quick Start Ask the agent to write a GDScript player controller with type hints, exported movement variables, and a health signal following the gdscript-patterns conventions.
