What problem does it solve? Game UI codebases drift into inconsistency when multiple developers create panels, prefabs, and components without shared rules, causing Z-order bugs, theme mismatches, and unmaintainable prefab structures. ## Core Features & Use Cases - Layered UI Architecture Rules: Defines the Screen/Overlay/Modal layer model under a single UIManager Canvas, with fade transitions and mutual exclusion rules. - Prefab and Component Standards: Mandates base prefabs with pre-wired references, Prefab Variants only for structural differences, and method-based encapsulation instead of exposing raw Unity components. - Theme and Color System: Routes all colors through UIThemeSO with color roles (primary/surface/onPrimary) and UIColorStyle switching, including Edit-mode preview via [ExecuteAlways]. - Use Case: When adding a new settings panel to the game, follow the conventions to register a UIPanelId enum value, build the prefab without a nested Canvas, wire theme color roles, and hook scene transitions through TransitionWithLoading. ## Quick Start Apply the gui-conventions rules to create a new UGUI screen prefab with theme colors and register it in the UIManager.
