Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When a user wants to turn an existing web React app (Next.js/Vite/CRA) into a native iOS/Android app with Expo, reuse web code incrementally, or map web idioms (DOM, CSS, React Router) to native.
migration-progress.md) bucketing screens.@expo/ui and expo-router, one per pass.agent-browser and argent.An end-to-end migration plan and execution loop that keeps the app shippable at every step, progressively replacing web screens with native ones while reusing code.
Use Cases
A startup has a Next.js web app and wants a mobile app without rewriting from scratch. They use this skill to assess routes, scaffold an Expo shell, and ship the web UI in a DOM-component shell on day one. Then they nativize high-value screens incrementally. The skill keeps the app shippable throughout and reuses most web code, saving months of rebuild.
A team with a Vite React dashboard needs to verify mobile parity. Using the skill's workflow, they port screens into a DOM shell, then redesign hot screens with @expo/ui. They drive the web original with agent-browser and the native build with argent to compare content and behavior each pass. This catches blank renders a build would miss and ensures native feel.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File