Run any Skill in Manus with one click

ue5-mobile-rendering

Stars0

Forks0

UpdatedApril 17, 2026 at 19:56

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.

Installation

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.

Run Skill in Manus

Source

strmt7

strmt7/project_air_defense

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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

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

More from this repository

same repository

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

ue5-mobile-ui

strmt7/project_air_defense

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-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-rendering
description	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.

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