Consolidated expert library for professional Godot 4.x game and application development. Orchestrates 94 specialized blueprints through architectural…
Godot Master: Lead Architect Knowledge Hub Every section earns its tokens by focusing on Knowledge Delta — the gap between what Claude already knows and what a senior Godot engineer knows from shipping real products. 🧠 Part 1: Expert Thinking Frameworks "Who Owns What?" — The Architecture Sanity Check Before writing any system, answer these three questions for EVERY piece of state: Who owns the data? (The StatsComponent owns health, NOT the CombatSystem) Who is allowed to change it? (Only the owner via a public method like apply_damage()) Who needs to know it changed? (Anyone listening to the health_changed signal) If you can't answer all three for every state variable, your architecture has a coupling problem. This is not OOP encapsulation — this is Godot-specific because the signal system IS the enforcement mechanism, not access modifiers.
don't have the plugin yet? install it then click "run inline in claude" again.