JGengine UI

Ownership

This skill owns player-facing presentation: HUDs, menus, overlays, layout, responsive behavior, accessibility, touch/controller presentation, feedback, previews, and UI chrome. World rendering belongs to jgengine-world; state ownership stays in gameplay/combat.

Search capabilities.md, use api.md for signatures, and open reference.md for component recipes. Visual polish uses references/visual-scorecard.md.

Canonical workflow

1. Define the real UI states: attract/menu, live play, pause, results, empty/error, and relevant overlays.
2. Read state through selectors/hooks; keep simulation mutation behind commands.
3. Compose headless data, renderer, and chrome where a second presentation is plausible.
4. Make keyboard, pointer, touch, controller, focus, and screen-reader behavior explicit.
5. Add preview fixtures using the real components for fast deterministic capture.
6. Verify desktop and mobile layouts through jgengine-verify.

Product rules