Godot Gdscript Architect

The problem

Standard LLMs often generate deprecated Godot 3 patterns like yield() or KinematicBody2D when you need Godot 4 code. This leads to broken builds, runtime errors in physics processing, and spaghetti node hierarchies that ignore modern composition best practices.

What it does

• Enforces Godot 4.x syntax including await, CharacterBody2D, and static typing for signals and arrays.
• Implements scene composition patterns using @export-driven design to replace fragile get_node() paths.
• Generates reusable component-based systems like health controllers, state machines, and inventory resources.
• Audits existing GDScript for performance bottlenecks and Godot 3-isms.
• Guides the architecture of complex systems using Resources for data-driven design instead of giant singletons.

Why this beats prompting it yourself

Generic prompts fail to catch subtle Godot 4 changes, such as move_and_slide() requiring a velocity return or the move from string-based signal connections. This skill provides an encoded set of strict architectural rules that prevent technical debt before it is written.

Use cases

• Building a modular player controller with coyote time and jump buffering using CharacterBody2D.
• Creating a node-based state machine for enemy AI behavior transitions.
• Designing a data-driven inventory system using Resource subclasses for item metadata.
• Refactoring a Godot 3 project to 4.x by identifying and replacing deprecated API calls.

Known limitations

Focuses primarily on GDScript and scene architecture. It does not provide specialized support for C# or low-level GDExtension development.