What problem does it solve? Godot 4 game development spans dozens of domains—combat, networking, UI, physics, save systems, exports—and developers often apply inconsistent patterns or reinvent solutions. This Skill acts as a router that maps any Godot task to the correct specialized sub-skill with vetted scripts and anti-pattern rules. ## Core Features & Use Cases - Task-to-Sub-Skill Routing: A decision table maps tasks (procedural generation, rollback netcode, hitboxes, theming, save/load, CI exports) to dedicated godot-* sub-skills under references/. - Production Patterns with Guardrails: Each sub-skill ships mandatory GDScript scripts (e.g., damage_data.gd, health_component.gd, save_migration_manager.gd) plus explicit NEVER-do rules for common engine pitfalls. - Use Case: While building a multiplayer FPS in Godot 4.7, ask how to implement hitscan weapons; the router directs you to godot-raycasting-queries and godot-combat-system for exclusion-optimized raycasts and DamageData-based hit resolution. ## Quick Start Ask the agent to implement a Godot feature such as a save system or hitbox combat, and it will route to the matching sub-skill and follow its mandatory scripts.