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.

Aller à l'installation

Dépôt: strmt7/project_air_defense
Dernière activité de la source: 13 avril 2026 à 19:08
Langue détectée de SKILL.md: anglais
Étoiles: 0
Forks: 0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/strmt7/project_air_defense --skill ue5-mobile-ui

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’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-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.

2026-04-13

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

Tout voir dans ce dépôt

UE5 Mobile UI

Load first

AGENTS.md

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

docs/planning/ue5-visual-acceptance.md

ue5/ProjectAirDefenseUE5/README.md

Rules

Use UMG or CommonUI for every player-facing menu, HUD, settings surface, or modal. Reserve Canvas-only drawing for debug overlays, proof tooling, or temporary migration aids.

Treat the visible product as touch-first. Hidden keyboard bindings may remain for automation, verification, or editor debugging, but do not show keyboard instructions in player-facing copy.

Use safe-zone-aware layout for any edge-anchored surface. Prefer USafeZone or equivalent viewport-safe-zone handling over manual magic numbers.

Keep the playfield readable. Prefer segmented corner clusters and compact drawers over full-width bars that block sky, horizon, or incoming threats.

Keep copy short. Use action-first labels and remove redundant explanatory text before shrinking font size.

Prefer layout containers over deeply nested Canvas Panels. Use Canvas only at the root when exact anchoring or layered composition is necessary.

Prefer event-driven UI updates over bound attributes or per-frame polling.

Use invalidation and retained rendering for mostly static widgets, and keep frequently changing widgets isolated.

For simultaneous mobile action buttons, default to non-focusable buttons unless there is a verified focus-navigation requirement.

Avoid Unreal's default touch interface unless the design explicitly depends on it. It can conflict with UMG and consume screen space needed by the actual game UI.

Every visible layout change needs screenshot proof in landscape smartphone framing.

Preferred stack

CommonUI + UMG for major menu stacks, modal flows, and routed input.

Plain UMG for compact HUD elements and project-specific touch widgets when CommonUI would add unnecessary complexity.

Slate only for editor tools or engine-level custom widgets.

Done means

the visible UI reads as mobile-first in landscape

no player-facing surface depends on keyboard instructions

safe zones are respected

the playfield remains the priority visual surface

touch actions are large, distinct, and verified from screenshots or runtime proof