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.

Jump to install

Repository: strmt7/project_air_defense
Last source activity: April 17, 2026 at 19:56
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-mobile-rendering

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

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