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.

الانتقال إلى التثبيت

المستودع: strmt7/project_air_defense
آخر نشاط في المصدر: ١٧ أبريل ٢٠٢٦ في ١٩:٥٦
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٠
التفرعات: ٠

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

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

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

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

عرض الكل من هذا المستودع

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