Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

ue5-mobile-ui

Estrelas0

Forks0

Atualizado13 de abril de 2026 às 19:08

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

strmt7

strmt7/project_air_defense

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	ue5-mobile-ui
description	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.

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

Mais deste repositório

mesmo repositório

ue5-mobile-rendering

strmt7/project_air_defense

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-170

ue5-commonui-menu-systems

strmt7/project_air_defense

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-130

ue5-mobile-gameplay

strmt7/project_air_defense

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-130

verification-loop

strmt7/project_air_defense

State the narrowest correct verification lane and report exactly what passed.

2026-04-120

android-visual-qa

strmt7/project_air_defense

Use when validating Project Air Defense with screenshots, OCR, template matching, or live emulator navigation, especially when libGDX SurfaceView content is not visible in the Android accessibility tree.

2026-04-120

android-3d-air-defense

strmt7/project_air_defense

Use this skill when building, debugging, balancing, profiling, or visually upgrading the Project Air Defense Android 3D missile-defense prototype, especially for libGDX battle flow, mobile rendering quality, interception logic, HUD ergonomics, and emulator-verified Android fixes.

2026-04-110

name	ue5-mobile-ui
description	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.

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