godot-autoload-architecture — Claude Code skill: Godot AutoLoad design

What godot-autoload-architecture does

The skill hands your agent a set of rules plus ready-made scripts for Godot singletons. Among them: autoload_init_order_diag.gd for checking boot sequence, singleton_dependency_diagram.gd for mapping who may call whom, global_event_bus.gd for cross-system events, and safe_scene_switcher.gd for scene changes owned by an AutoLoad. Non-Node services go through service_locator.gd and service_registry.gd, registered with Engine.register_singleton.

A large part of the text is a list of things not to do. AutoLoads boot top to bottom in Project Settings, so an upper singleton must not call a lower one from _ready(). Circular dependencies between singletons hang Godot on the splash screen. Touching another AutoLoad inside _init() is out too, because that neighbour may not exist yet.

Scripts cover data that has to survive change_scene_to_file() — inventory, settings — and lazy instantiation when eager boot cost hurts. For background threads that read or write global state there is thread_safe_global_access.gd with a mutex and call_deferred. Registration and default-value checks live in autoload_reference_checker.gd and singleton_health_check_test.gd; run those in debug and CI.