godot-composition-apps — Claude Code skill for Godot UI architecture

What godot-composition-apps does

This skill covers Control-heavy interfaces in Godot: EditorPlugin docks, tool windows, forms, settings panels. The root node acts as an orchestrator. It holds no business math — it listens to component signals and calls component methods. Communication runs one way: components signal upward, the orchestrator calls downward. Sibling components never talk to each other directly.

A set of starter scripts ships with it. comp_rock_test_boilerplate.gd runs the rock test: attach the candidate script to a literal rock and see whether it still works. comp_orchestrator_base.gd gives you the signal-up wiring skeleton, comp_logic_visual_syncer.gd keeps logic away from AnimationPlayer and Theme, and comp_persistence_component.gd handles saveable state through the Saveable group. Dependency injection, resource-backed config and a step sequencer for wizards and export pipelines round it out.

Gameplay entities are out of scope on purpose. Player, Enemy, Weapon and Hitbox belong to the separate godot-composition skill, so watch for an agent applying orchestrator rules to a character where they do not fit. Wire components through @export or %UniqueNames rather than get_node("Path/To/Child") and get_parent() — brittle node paths break the moment you move a node in the scene tree.