What problem does it solve? Upgrading a NativePHP Mobile app from v3 (Livewire/Volt/Flux in a web view) to v4 native EDGE UI involves undocumented package renames, silent rendering failures, font and theme-push timing traps, and layout behaviors that differ from CSS — most of which fail without any error message. ## Core Features & Use Cases - Phased migration plan: Covers composer package moves (nativephp/native-ui → nativephp/mobile-ui), plugin registration, Livewire removal ordering, scaffolding, screen conversion, and cutover. - Silent-failure diagnosis: Documents layout traps verified from renderer source — empty columns painting nothing, anchored absolute children, zero-inset anchoring bugs, and silently dropped Tailwind classes. - Fonts and theme guidance: Explains the native:font command location, font alias registration, and the theme-push timing fix that resolves system-font fallback. - Use Case: A team with a Livewire-based NativePHP v3 mobile app uses this Skill to plan and execute a full cutover to native EDGE screens, porting tests to Native::test() with FakeBridge and avoiding weeks of silent-rendering debugging. ## Quick Start Ask the agent to upgrade my NativePHP mobile app from v3 to v4 native EDGE UI following the phased migration plan.