ue5-commonui-menu-systems

Use when changing a major UE5 front-end menu, options flow, modal stack, routed input surface, or layered smartphone-first menu architecture. Applies to CommonUI adoption decisions, activatable-widget stacks, menu settings flows, and player-facing mobile front-end structure.

Jump to install

Repository: strmt7/project_air_defense
Last source activity: April 13, 2026 at 20:48
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/strmt7/project_air_defense --skill ue5-commonui-menu-systems

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

ue5-mobile-rendering

Use when changing UE5 smartphone rendering, graphics settings, anti-aliasing, ambient occlusion, reflections, post-process, device profiles, or mobile performance tiers. Applies when exposing graphics options to players or claiming that a visual feature works on-device.

2026-04-17

ue5-mobile-gameplay

Use when changing UE5 mobile gameplay flow, menu-to-battle state, touch input routing, hidden debug bindings, deterministic simulation ownership, or verification for a smartphone-first game. Applies to controller state, battle bootstrap, Enhanced Input, and automation-backed gameplay checks.

2026-04-13

ue5-mobile-ui

Use when changing any UE5 player-facing menu, HUD, pause surface, settings surface, touch control, or smartphone layout. Applies to UMG/CommonUI choice, safe zones, touch hit targets, information density, keyboard-hint suppression, and keeping the playfield visible on phones.

2026-04-13

View all from this repository

UE5 CommonUI Menu Systems

Load first

AGENTS.md

docs/reference/ue5-mobile-agent-skill-sources.md

.agents/skills/ue5-mobile-ui/SKILL.md

docs/planning/ue5-gameplay-migration-matrix.md

Rules

Use CommonUI for large multi-screen menu stacks, routed modal flows, and settings navigation when plain UMG would otherwise create manual state spaghetti.

Keep plain UMG for compact in-battle HUD elements and project-specific overlays when CommonUI would add unnecessary runtime weight.

Treat the menu shell as a product surface, not a debug overlay. Title, actions, settings, and source/status information must be readable in landscape without burying the city view.

Keep menu copy short and action-first. Prefer one primary action, one secondary action, and compact status chips over multiple explanation paragraphs.

Keep buttons large, non-focusable by default for touch, and safe-zone aware.

If a settings surface exists, every visible option must map to real runtime behavior or persistence. No placeholder settings.

When adding a new menu layer, define the owning state transition first. Do not let widgets invent their own routing logic.

Screenshot-proof every front-end state that a player can actually reach.

Preferred stack

CommonUI activatable widgets for front-end stacks and routed settings menus.

Plain UMG for the in-battle HUD, radar, and compact drawers.

Enhanced Input or controller-owned state only for debug bindings and verification hooks, never as player-facing instructions.

Done means

the front-end menu is touch-first and landscape-first

action hierarchy is clear from one screenshot

settings flow is real, not decorative

menu routing does not fight gameplay state

name	ue5-commonui-menu-systems
description	Use when changing a major UE5 front-end menu, options flow, modal stack, routed input surface, or layered smartphone-first menu architecture. Applies to CommonUI adoption decisions, activatable-widget stacks, menu settings flows, and player-facing mobile front-end structure.