What problem does it solve? Moving an existing web React app (Next.js, Vite, CRA) to native mobile has no transpiler — it requires a screen-by-screen migration strategy, and teams often get stuck deciding what to port, how web idioms map to native, and how to verify the result. ## Core Features & Use Cases - Strangler-fig migration plan: Assess and bucket every route (port-as-is, nativize-now, nativize-later, hybrid), ship a DOM-component shell on day one, then nativize screens by value. - Web-to-native idiom maps: Reference tables translate DOM elements, CSS, routing, storage, networking, and third-party SDKs (Stripe, maps, analytics) to their Expo/React Native equivalents. - Native redesign playbook: Maps web UX patterns to @expo/ui SwiftUI/Compose components, Expo Router navigation, haptics, and motion so screens feel OS-native. - Run-verified parity checks: Compare the running web app (agent-browser) against the native screen (argent/simulator) for content and behavior, including motion recordings. - Use Case: You have a Next.js SaaS dashboard and want an App Store app. The skill produces a worklist, shells the whole UI in DOM components immediately, then nativizes the hot screens one per iteration until the worklist is empty. ## Quick Start Ask the agent to use the expo-web-to-native skill to assess your web React repository and produce a migration worklist, then drive the screen-by-screen native migration as a goal loop.
