What problem does it solve? Verifying mobile app changes requires launching simulators or emulators, standing up isolated backend state, pairing devices, and driving the UI, which is error-prone and easy to do against shared or stale environments. This Skill provides a repeatable end-to-end workflow for testing T3 Code Mobile changes on a real iOS Simulator or Android Emulator without touching shared state. ## Core Features & Use Cases - Platform and launch-path selection: Picks a viable iOS or Android target based on host tooling and decides whether to reuse a dev client or rebuild native code based on what changed. - Disposable environment setup: Seeds Git projects, starts a headless backend against an isolated base directory, and issues single-use pairing tokens per device. - Semantic UI driving and verification: Uses XcodeBuildMCP snapshots on iOS and uiautomator or adb input on Android, captures screenshots as evidence, and cleans up only the processes it started. - Use Case: After changing a native dependency in the mobile app, use this Skill to rebuild the Android dev client, pair an emulator to a fresh seeded backend, exercise the affected flow, and return a screenshot proving the fix. ## Quick Start Use the test-t3-mobile skill to launch T3 Code Dev on an available simulator or emulator against an isolated backend and verify my recent mobile UI change.
