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.

Ir a la instalación

Repositorio: strmt7/project_air_defense
Última actividad en el origen: 17 de abril de 2026 a las 19:56
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

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

Ver todos los de este repositorio

UE5 Mobile Rendering

Load first

AGENTS.md

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

docs/planning/ue5-visual-acceptance.md

ue5/ProjectAirDefenseUE5/Config/DefaultEngine.ini

ue5/ProjectAirDefenseUE5/Config/DefaultGame.ini

Rules

Expose only settings that map to real engine behavior on the active renderer and platform. Do not ship placebo toggles.

Bind user-facing graphics controls through UGameUserSettings, device profiles, or verified project CVars, not ad-hoc console spam.

Verify feature support against Epic's current mobile rendering and performance docs before exposing AA, AO, reflections, shadows, post-process, or similar toggles.

Use the Mobile Previewer and device-profile-driven preview before claiming a mobile visual result.

Prefer stable frame time, legibility, and truthful materials over desktop-only effects.

Ray tracing may be exposed only as an opt-in request path and must remain off by default; it is not the Android mobile baseline.

No static gameplay backdrops. The battle scene must stay geometry-driven, tileset-driven, or material-driven.

Keep the disk footprint controlled during iteration: one packaged build, no stale staged-build duplicates, no redundant dataset copies.

Every rendering or settings change needs serial proof, not overlapping runtime launches.

Graphics-settings contract

Anti-aliasing, ambient occlusion, reflections, shadows, post-process, and similar labels must report what backend state was actually applied.

Hide or relabel options that are unsupported on the current mobile path instead of pretending they work.

Device-tier defaults must come from measured hardware or documented device-profile policy.

Done means

user-visible graphics settings are truthful

mobile support claims are backed by preview or runtime proof

scene fidelity improves without breaking frame-time or storage discipline