godot-claritylisted

# Godot Clarity Work from the project and engine as evidence. Treat scripts, scenes, Resources, project settings, imports, and runtime behavior as one system. Never present static inspection as engine-verified behavior. ## Choose the operating mode - **Create:** establish a small project contract, build one playable vertical slice, then extract only proven abstractions. - **Extend:** trace the existing feature across every serialized and scripted dependency, then make the smallest cross-file-complete change. - **Debug:** preserve a deterministic reproduction, find the first causal failure, change one contract, and rerun the same proof. - **Review:** report concrete correctness, lifecycle, compatibility, safety, and verification gaps without rewriting the project unless asked. For creation work, read [project workflow](references/project-workflow.md) before generating files. When the requested slice includes a common gameplay feature, also read [gameplay patterns](references/gameplay-patterns.md) and adapt the smallest matching contract. For pixel-art presentation or a 2D platformer, read the [practical 2D cookbook](references/2d-cookbook.md) before writing project settings or movement. For an established project, preserve coherent local conventions unless they cause the bug or conflict with the request. ## Establish the project contract 1. Locate the real root from `project.godot`, or choose it explicitly for a new project. 2. Read repository instructions and preserve u