🇺🇸English
GDScript Mastery
Expert guidance for writing performant, maintainable GDScript following official Godot standards.
Available Scripts
Expert performance optimization using statically typed Arrays and Dictionaries.
Advanced list processing using reduce(), all(), and any() with clean lambda syntax.
Best practices for using the as operator for crash-proof object identification.
Enforcing type safety across script boundaries using strictly typed signal arguments.
Injecting extra context into signal callbacks using Callable.bind().
Safely discarding unneeded signal arguments using Callable.unbind().
Managing complex asynchronous flows and timers using await without thread-blocking.
Eliminating memory reallocation lag by pre-sizing large arrays with resize().
Using static var for global state management as an alternative to heavy Autoloads.
The correct pattern for erasing dictionary keys while iterating to avoid runtime errors.
NEVER Do in GDScript
- NEVER use
@onready and @export on the same variable — Initialization order will cause @onready to overwrite the Inspector value [1].
- NEVER modify a Dictionary's size while iterating it — Use
dict.keys().duplicate() or iterate a clone to safely erase elements [2, 3].
- NEVER use string-based
connect("signal", ...) — Always use the Signal object syntax (button.pressed.connect(...)) for compile-time safety [4].
- NEVER attempt to override non-virtual native engine methods — Overriding
queue_free() or get_class() is unsupported and will be ignored by engine callbacks [5, 6].
- — Fetching paths every frame stalls the CPU. Cache and use [7, 8].
Core Directives
1. Strong Typing
Always use static typing. It improves performance and catches bugs early. Rule : Prefer var x: int = 5 over var x = 5. Rule : Always specify return types for functions: func _ready() -> void:.
2. Signal Architecture
- Connect in
_ready(): Preferably connect signals in code to maintain visibility, rather than just in the editor.
- Typed Signals : Define signals with types:
signal item_collected(item: ItemResource).
- Pattern : "Signal Up, Call Down". Children should never call methods on parents; they should emit signals instead.
3. Node Access
- Unique Names : Use
%UniqueNames for nodes that are critical to the script's logic.
- Onready Overrides : Prefer
@onready var sprite = %Sprite2D over calling get_node() in every function.
4. Code Structure
Follow the standard Godot script layout:
extendsclass_namesignals / enums / constants@export / @onready / properties_init() / _ready() / _process()
Common "Architect" Patterns
The "Safe" Dictionary Lookup
Avoid dict["key"] if you aren't 100% sure it exists. Use dict.get("key", default).
Scene Unique Nodes
When building complex UI, always toggle "Access as Scene Unique Name" on critical nodes (Labels, Buttons) and access them via %Name.
Reference
- Official Docs:
tutorials/scripting/gdscript/gdscript_styleguide.rst
- Official Docs:
tutorials/best_practices/logic_preferences.rst
Related
- Master Skill: godot-master
Weekly Installs
80
Repository
thedivergentai/…c-skills
GitHub Stars
59
First Seen
Feb 10, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode77
gemini-cli74
codex74
github-copilot70
kimi-cli69
amp69
