expo-web-to-native
An agent skill by expo, from expo/skills. Tags: architecture, development, migration, mobile, react, web.
What it does
Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, window) map to native. This is the end-to-end migration guide; use the `expo-dom` skill for the DOM-component mechanism itself.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-web-to-native
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/expo-web-to-native ~/.claude/skills/expo-web-to-native
Safety box score
Grade D, elevated risk: 61 of 100 risk points, rated 2026-10-16. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This is a migration playbook for turning a web React app into an Expo native app, and it can drive code changes, device runs, package installs, and eventual store publishing. The main risks are broad publish/update authority, system-wide tool installation, and handling auth tokens while migrating web session assumptions to native.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It explicitly runs shell commands and package entrypoints like `npx expo start --ios`, `xcrun simctl`, `adb`, and `npx --yes submit-expo-feedback@latest`, so using it executes local commands and installed tools. |
| Network access | 2 (moderate) | It reaches out to remote services for installs and operations, including `npm i -g agent-browser`, `npm i -g @swmansion/argent`, `agent-browser open "<web-url>/<route>"`, and the optional Expo feedback submission command. |
| Filesystem reach | 2 (moderate) | It creates and updates project files such as `migration-progress.md` and `migration-goal.md`, and the migration steps require editing route and app source files throughout the repo. |
| Secrets & credentials | 2 (moderate) | It explicitly migrates browser auth to native secret storage, e.g. `cookies()` / `document.cookie` to `expo-secure-store` and bearer headers, so the workflow can involve credential material. |
| Privilege & persistence | 2 (moderate) | The verification setup installs tools globally with `npm i -g agent-browser` and `npm i -g @swmansion/argent`, which changes the user’s environment outside the project. |
| Instruction hijack surface | 1 (low) | The goal-loop reference tells the agent to re-read the skill every iteration, and the feedback command uses `npx --yes` to auto-answer prompts; that is automation pressure, though not an overt prompt-override attack. |
| Irreversible actions | 3 (high) | The stated endgame includes `eas-app-stores` and `EAS Update`, which gives the workflow the ability to publish builds and push OTA updates—high-blast-radius actions inherent to the skill’s purpose. |
| Transparency | 1 (low) | Some actions rely on fetched registry code and unpinned latest installs such as `npx --yes submit-expo-feedback@latest` and `npm i -g ...`, so the executed code is not fully reviewable from the skill files alone. |
Before installing
- Read `references/verify-on-device.md` and decide whether you accept global installs (`npm i -g ...`) on this machine.
- Confirm whether the app uses cookie/session auth; step 5 assumes you can move credentials into `expo-secure-store` and bearer headers.
- If you do not want publishing access, stop before step 6 (`eas-app-stores` / `EAS Update`).
- Run the migration in a scratch branch or disposable clone first, because it will edit route files and write `migration-progress.md`.
Rated 2026-10-16 by an automated review of 6 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-web-to-native/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- expo-dom — Framework (OSS). Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
- expo-brownfield — Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app.
- launch-with-aws — Migrates vibe-coded web applications to AWS.
- aws-amplify — Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).
- csharp-developer — Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing.
- i18n-expert — This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar.