[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MZJNCMPY6Y8P9AYCTDQVT":3,"skill-same:01M71MZJNCMPY6Y8P9AYCTDQVT":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71MZJNCMPY6Y8P9AYCTDQVT","eas-simulator",null,"EAS service (paid). Run and control a user's app on a remote iOS\u002FAndroid simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run\u002Finstall\u002Fscreenshot my app', 'I'm on Linux\u002FCursor and need an iOS device', 'no sim on this box \u002F headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud\u002Fremote\u002Fshareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build\u002FUpdate, web preview, or physical devices.","pattanation\u002FNorvik","pattanation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235419268?v=4","01M71M5THHYYB15ME8R2E4FCZG","Patta","01M71M5TJM1NDM992M8PDKYR2K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Feas-simulator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"eas simulator","remote","xcode","browser","api","preview","studio","Bash","when","auto","host","only","local","ci","default","Android Studio","paid","headless","click","app","2026-11-10 10:56:23",false,"---\nname: eas-simulator\ndescription: \"EAS service (paid). Run and control a user's app on a remote iOS\u002FAndroid simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run\u002Finstall\u002Fscreenshot my app', 'I'm on Linux\u002FCursor and need an iOS device', 'no sim on this box \u002F headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud\u002Fremote\u002Fshareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build\u002FUpdate, web preview, or physical devices.\"\nversion: 1.0.0\nlicense: MIT\nallowed-tools: \"Bash(npx *eas-cli@*), Bash(npx *agent-device@*), Bash(npx expo *), Bash(eas *), Bash(expo *), Bash(xcodebuild*), Bash(pod*)\"\n---\n\n# EAS Simulator\n\n> **EAS service - costs apply.** EAS Simulator runs on Expo Application Services cloud infrastructure, a paid product with free-tier limits; remote simulator sessions use your plan's compute allowance. See https:\u002F\u002Fexpo.dev\u002Fpricing.\n\nEAS Simulator runs a remote iOS simulator or Android emulator on EAS infrastructure that you drive from your machine — from the CLI, from an AI agent (via `agent-device`), and from a browser preview. It's the unlock for **environments that can't run a simulator locally** (Linux boxes, cloud\u002Fbackground agents like Cursor Cloud), and for letting an agent *verify* a change on a real device instead of only reasoning about code.\n\nThe `simulator:*` commands are **experimental and hidden**, and need a recent eas-cli (≥ 20.3.0 as of writing) — which is why this skill runs everything via `npx --yes eas-cli@latest`. Flags and verbs may change; if a command fails, **`\u003Ccmd> --help` is authoritative.**\n\n## When to use\n\nThe frontmatter `description` carries the trigger phrases. In short: use this to get a user's app onto a **cloud** simulator and interact with it — especially from a Mac-less or cloud\u002Fsandbox agent. **Not** for local sims (`expo run:ios`, Xcode, Android Studio), store builds\u002Fsigning (that's EAS Build), or physical devices. For the macOS case, see *Cloud vs local* next.\n\n## Cloud vs local: decide this first\n\n- **Non-macOS** (Linux \u002F CI \u002F cloud sandbox like Cursor Cloud, detect via `uname -s` ≠ `Darwin`): the only way to get a sim — **just proceed.**\n- **macOS:** local sims exist and a cloud session costs money + latency, so **ask first** (\"a remote cloud sim — to share a live preview, offload, or test an iOS version you lack — or just run locally?\") unless the user explicitly said cloud\u002Fremote\u002Fshareable.\n- Always honor an explicit choice; for \"run it locally\" hand off to `expo run:ios` \u002F Xcode.\n\n```bash\n# Programmatic detection — run this to decide before doing anything else:\nif [ \"$(uname -s)\" != \"Darwin\" ] || ! xcrun --find simctl &>\u002Fdev\u002Fnull 2>&1; then\n  echo \"no local sim — proceed with EAS Simulator\"\nelse\n  echo \"local sim available — ask the user (cloud or local?)\"\nfi\n```\n\n## Prerequisites\n\n- **Run every `eas` command via `npx --yes eas-cli@latest …`** — guarantees a CLI new enough to have `simulator:*` (a global `eas` is often too old), and `--yes` skips npx's prompt. (Bare `eas` is fine if `eas --version` is current.)\n- **Authenticated.** Interactive machine → `npx --yes eas-cli@latest login`. **Cloud sandbox \u002F CI \u002F headless agent has no browser login — set `EXPO_TOKEN`** (expo.dev → Account → Access Tokens) in the env instead. Verify either way with `npx --yes eas-cli@latest whoami`.\n- Run from an Expo **project directory.** A fresh app needs one-time setup: `npx --yes eas-cli@latest init` to create\u002Flink the project (when there's no `projectId`), and **set `ios.bundleIdentifier`** in app config if it's missing — a fresh `create-expo-app` often has none, and `prebuild`\u002F`eas build` need it (they prompt or fail without it; e.g. `dev.\u003Cowner>.\u003Cslug>`). Read current config with `npx expo config --json` (it may live in `app.config.js`). The first Mode-C run is slow (native build); later runs reuse it.\n- A controller to drive the device. This skill uses **agent-device** (open source, MIT), run on demand via `npx agent-device@latest` — nothing globally installed. **argent** is an alternative (`--type argent` in `simulator:start`); see [references\u002Fcontrollers.md](.\u002Freferences\u002Fcontrollers.md).\n- **`.env.eas-simulator`** is written\u002Fmanaged by eas-cli (not this skill): it holds the session id (`EAS_SIMULATOR_SESSION_ID`) + the daemon URL\u002F**token**, so `get`\u002F`stop`\u002F`exec` default to that session (usually **omit `--id`**; pass `--id \u003Cid>` to target another). It carries a **token → keep it gitignored** (eas-cli marks it \"do not commit\" but may not add the ignore rule, and a fresh app's `.gitignore` won't cover it — add `.env.eas-simulator` if missing).\n- `--max-duration-minutes` is paid-plan only; otherwise a default applies.\n\n## The core loop (always the same)\n\nA session is: **start → (install your app) → drive → stop.** `eas-cli` owns the *session*; the device *verbs* (open\u002Ftap\u002Fscreenshot) come from the controller, which `npx --yes eas-cli@latest simulator:exec` runs for you with the session's connection env loaded.\n\n```bash\n# 1. Start a session (boots the remote sim + agent-device daemon; writes .env.eas-simulator).\nprintf '# managed by eas-cli\\n' > .env.eas-simulator   # clear any stale session first\nnpx --yes eas-cli@latest simulator:start --platform ios --type agent-device --non-interactive\n#    Then confirm it's live: simulator:get --json → status IN_PROGRESS (bounded poll in run-your-app.md).\n\n# 2. Drive it through `exec` (loads the session env, then runs the command you give it).\n#    agent-device runs on demand via npx — nothing installed globally.\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest open \u003Capp-or-url> --platform ios\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest snapshot -i          # interactive UI tree → @e1, @e2 refs\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest press @e2            # tap a ref (NOTE: 'press', not 'tap')\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest screenshot .\u002Fshot.png\n\n# 3. Stop (ends billing; tears down the VM) and reset the dotenv. Omit --id to target the dotenv session.\nnpx --yes eas-cli@latest simulator:stop\nprintf '# managed by eas-cli\\n' > .env.eas-simulator\n```\n\nTo **watch** it live, hand the user the `webPreviewUrl` that `start` prints (an `--type agent-device` iOS session runs serve-sim alongside the daemon, so it emits one — agent control *and* a browser preview in one session; Android has no preview, and `--type serve-sim` is preview-only). **This URL is for the *user's* browser — you cannot open it for them, and it must never touch the sim:**\n- **\"Open it here\" (Cursor\u002FVS Code)** → print the URL on its own line and tell the user to open Simple Browser (`Cmd\u002FCtrl+Shift+P` → \"Simple Browser: Show\") and paste it. Then **stop**: do not shell out to a system browser or a Cursor\u002FVS Code URL handler, and do not ask \"did a tab appear?\" — you can't confirm it, the handoff is done.\n- **Never `open` the `webPreviewUrl` on the sim.** It's a browser preview, not a deep link and not an `agent-device open` argument; routing it to the device renders a browser-in-a-browser (a real past failure).\n- **Headless agent** (no display) → just return the URL as the deliverable.\n- **Keeping it alive for the user to drive** → bound it: start with `--max-duration-minutes N` so it auto-stops; tell them it bills until stopped and when it auto-stops; offer to reopen\u002Fextend when it ends. (This is the one case where \"stop right away\" doesn't apply; one-shot `screenshot`\u002F`get` runs still stop immediately.)\n\n`start` also prints a job-run URL.\n\n## Commands at a glance\n\n| Command | Purpose |\n|---|---|\n| `npx --yes eas-cli@latest simulator:start --platform ios\\|android [--type agent-device\\|argent\\|serve-sim] [--package-version X] [--max-duration-minutes N] [--non-interactive] [--json]` | Create a session; boot the sim + controller; write `.env.eas-simulator`; print `webPreviewUrl` + job-run URL |\n| `npx --yes eas-cli@latest simulator:exec \u003Ccmd> [args…]` | Load `.env.eas-simulator`, then run `\u003Ccmd>` with that env. The bridge to the controller. |\n| `npx --yes eas-cli@latest simulator:get [--id] [--json]` | Session status + connection details. **Use this to confirm readiness** (see *Operating principles*). |\n| `npx --yes eas-cli@latest simulator:list [--status …] [--type …] [--platform …]` | List an app's sessions |\n| `npx --yes eas-cli@latest simulator:stop [--id]` | Stop a session (idempotent) |\n\n## Running the user's app — pick a mode\n\nThe remote sim boots **blank — no Expo Go, no apps.** Install a build, then drive it — but **match the build *type* to the goal first** (the box below); that's where live-session runs derail. Full sequences: [references\u002Frun-your-app.md](.\u002Freferences\u002Frun-your-app.md) — read before running a mode.\n\n> **Match the build to the goal before installing anything — this is where live-session runs derail.** Two traps, same root (grabbing a build that doesn't fit the request):\n> 1. **Wrong type.** Live edits (Mode C) **require a dev build.** A *static* build — a local Release (A), the default EAS sim build (B), or **any build left on the sim from an earlier screenshot run** — freezes its JS at build time and **can never hot-reload.** For a live request, **ignore existing builds entirely** and install a **dev** build (local Debug, or an EAS build with `developmentClient: true`). Never reconnect Metro to a static build hoping it'll reload — it won't.\n> 2. **Stale.** A static look must match current source — reuse only a fingerprint-matched build, else build fresh; reuse is explicit-only.\n>\n> So a leftover EAS\u002Frelease build is **not** a shortcut for \"iterate live\" — it's the wrong binary. The fact that a build *exists* never makes it the right one.\n\n| Mode | What it is | Choose when | Live edits? |\n|---|---|---|---|\n| **A — Local release build** | Build a Release `.app` locally, `agent-device install` it (uploads) | User has a Mac toolchain and wants a quick \"run my current code on a cloud device\" | No (rebuild to see changes) |\n| **B — EAS build** (rare, explicit-only) | `eas build` a simulator build, `agent-device install-from-source \u003Curl>` (the VM downloads it) | **Only when explicitly asked** — the user names an existing\u002FEAS build, or wants a static EAS artifact for CI\u002Fsharing. Not for \"show me\"\u002F\"iterate\" (use C). Sim builds need no credentials. | No |\n| **C — Local dev build + tunnel** | Dev (Debug) build + `EXPO_UNSTABLE_TUNNEL_V2=1 expo start --tunnel` + connect the dev client to Metro | **The agentic edit-and-see loop** — change code and see it live (Fast Refresh) | **Yes** |\n\nQuick decision — **default to C; A and B are explicit-only:**\n- **C (almost everything):** iterate, interact, poke the app, live edits — *and* most \"show me my app\" (current code needs a build anyway, so live+current wins). Mac → dev client builds locally; no Mac → build it on EAS (`developmentClient: true`). **Unsure → C.**\n- **A:** only an explicit one-shot **static** screenshot on a Mac.\n- **B:** only when the user names an existing\u002FEAS build or wants a static EAS artifact (CI\u002Fsharing) — see the box above for why a static build is the wrong tool for \"iterate.\"\n\n## Driving the device (agent-device)\n\n`agent-device` is the controller. Common verbs (run each as `npx --yes eas-cli@latest simulator:exec npx agent-device@latest \u003Cverb>`):\n\n| Verb | Does |\n|---|---|\n| `apps --platform ios` | List installed apps (the blank sim shows none) |\n| `install \u003CappId> \u003Cpath> --platform ios` | Install a local `.app` (uploads it) |\n| `install-from-source \u003Curl> --platform ios` | Install from a URL — the VM downloads it (use for EAS artifacts) |\n| `open \u003CappId\\|deep-link> --platform ios` | Launch an app (bundle id) or follow an app **deep link** (`exp+slug:\u002F\u002F…`). **Not** for the `webPreviewUrl` — that's a browser preview for the user, never the device. |\n| `snapshot -i` | Interactive accessibility tree → `@e1`-style refs |\n| `press \u003Cref\\|selector>` | Tap (e.g. `press @e2` or `press 'label=\"Open\"'`) — **the tap verb is `press`, not `tap`** |\n| `fill \u003Cref> \"text\"` | Type into a field |\n| `screenshot \u003Cpath>` | Capture the screen to a local PNG (downloaded from the daemon) — requires an app to be open (`open` first) |\n| `metro prepare` \u002F `metro reload` | Point a dev client at Metro \u002F reload (Mode C) |\n\nFor the full verb set and the `argent` controller alternative, see [references\u002Fcontrollers.md](.\u002Freferences\u002Fcontrollers.md).\n\n## Operating principles\n\nThe non-obvious mental model worth internalizing. Specific error→fix lookups (hung verbs, `tap`→`press`, `--platform`, `--json`, `pod install` locale, orphaned sessions, boot variability) live in [references\u002Ftroubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md).\n\n1. **Establish ground truth, then reset — don't patch-loop.** Never assume an existing session or Metro is yours or healthy. Before driving, confirm:\n   - **cwd** — you're in the intended Expo project dir (a misdirected `start`\u002F`exec` sessions the *wrong app* + drops a stray `.env.eas-simulator`; `pwd` \u002F check `app.json`).\n   - **session live** — `IN_PROGRESS` via `simulator:get --json` (a stopped session keeps its id + `remoteConfig`, so the dotenv alone isn't proof).\n   - **one Metro on `:8081`** — reuse if it's yours, else free the port before starting (run-your-app.md).\n   - **build fits intent** — a **release build can't live-reload**; if live edits are wanted and a release build is installed, **install the dev build, don't reconnect**.\n\n   If current code isn't rendering after your **first** connect, stop poking live state: **reset to baseline** (stop session → clear dotenv → kill Metro) and redo the mode **once**; a second failure → stop and report. Never restart Metro in place, reconnect more than once, rebuild the native client to fix a JS\u002Fconnection problem, or surface a preview URL while state is unknown. (A daemon drop — `ERR_NGROK_3200` \u002F `Remote daemon is unavailable` — is the same: reset, don't retry.)\n2. **`exec` is a wrapper, not a driver.** `simulator:exec` loads `.env.eas-simulator` and spawns the command you pass; the device verbs come from the controller (`npx agent-device@latest`). There is no `simulator:tap`.\n3. **Act immediately; don't park an idle session.** Sessions are short-lived — install and drive right after `start`. Leaving one idle drops the tunnel\u002Fdaemon (→ reset, per #1).\n4. **Stop on every exit path (billing) and reset the dotenv.** `--non-interactive` doesn't auto-stop, and a forgotten session bills until stopped. Don't `start` again to \"retry\" a slow boot — that orphans a second billed session.\n5. **Screenshot only the correct, fresh build.** Mode C only after the dev client connects to Metro; A\u002FB only from a build matching current source — reusing a pre-existing build is the #1 \"my edits don't show\" cause (see the build caveat above). (`9:41` in the status bar is the sim default, not staleness.)\n\n## Stop and clean up\n\nStop the session (ends billing) **and reset the dotenv** so a later run doesn't try to reuse the dead session:\n\n```bash\nnpx --yes eas-cli@latest simulator:stop          # omit --id → stops the dotenv session (or pass --id \u003Cid>)\nprintf '# managed by eas-cli\\n' > .env.eas-simulator   # clear the stale session id so it isn't reused\n# if you started Metro for Mode C, stop it too (Ctrl+C in its terminal, or kill the expo process)\n```\n\n## References\n\n- [references\u002Frun-your-app.md](.\u002Freferences\u002Frun-your-app.md) — full tested command sequences for modes A, B, and C (read before running a mode).\n- [references\u002Fcontrollers.md](.\u002Freferences\u002Fcontrollers.md) — agent-device verb reference and the `argent` alternative.\n- [references\u002Ftroubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md) — concrete errors and fixes.\n\nSource of truth: Expo docs and the `eas` \u002F `agent-device` CLIs (`npx --yes eas-cli@latest simulator:* --help`, `agent-device --help`). This skill teaches how to apply them; it doesn't replace them.\n","# EAS Simulator\n\n> **EAS service - costs apply.** EAS Simulator runs on Expo Application Services cloud infrastructure, a paid product with free-tier limits; remote simulator sessions use your plan's compute allowance. See https:\u002F\u002Fexpo.dev\u002Fpricing.\n\nEAS Simulator runs a remote iOS simulator or Android emulator on EAS infrastructure that you drive from your machine — from the CLI, from an AI agent (via `agent-device`), and from a browser preview. It's the unlock for **environments that can't run a simulator locally** (Linux boxes, cloud\u002Fbackground agents like Cursor Cloud), and for letting an agent *verify* a change on a real device instead of only reasoning about code.\n\nThe `simulator:*` commands are **experimental and hidden**, and need a recent eas-cli (≥ 20.3.0 as of writing) — which is why this skill runs everything via `npx --yes eas-cli@latest`. Flags and verbs may change; if a command fails, **`\u003Ccmd> --help` is authoritative.**\n\n## When to use\n\nThe frontmatter `description` carries the trigger phrases. In short: use this to get a user's app onto a **cloud** simulator and interact with it — especially from a Mac-less or cloud\u002Fsandbox agent. **Not** for local sims (`expo run:ios`, Xcode, Android Studio), store builds\u002Fsigning (that's EAS Build), or physical devices. For the macOS case, see *Cloud vs local* next.\n\n## Cloud vs local: decide this first\n\n- **Non-macOS** (Linux \u002F CI \u002F cloud sandbox like Cursor Cloud, detect via `uname -s` ≠ `Darwin`): the only way to get a sim — **just proceed.**\n- **macOS:** local sims exist and a cloud session costs money + latency, so **ask first** (\"a remote cloud sim — to share a live preview, offload, or test an iOS version you lack — or just run locally?\") unless the user explicitly said cloud\u002Fremote\u002Fshareable.\n- Always honor an explicit choice; for \"run it locally\" hand off to `expo run:ios` \u002F Xcode.\n\n```bash\n# Programmatic detection — run this to decide before doing anything else:\nif [ \"$(uname -s)\" != \"Darwin\" ] || ! xcrun --find simctl &>\u002Fdev\u002Fnull 2>&1; then\n  echo \"no local sim — proceed with EAS Simulator\"\nelse\n  echo \"local sim available — ask the user (cloud or local?)\"\nfi\n```\n\n## Prerequisites\n\n- **Run every `eas` command via `npx --yes eas-cli@latest …`** — guarantees a CLI new enough to have `simulator:*` (a global `eas` is often too old), and `--yes` skips npx's prompt. (Bare `eas` is fine if `eas --version` is current.)\n- **Authenticated.** Interactive machine → `npx --yes eas-cli@latest login`. **Cloud sandbox \u002F CI \u002F headless agent has no browser login — set `EXPO_TOKEN`** (expo.dev → Account → Access Tokens) in the env instead. Verify either way with `npx --yes eas-cli@latest whoami`.\n- Run from an Expo **project directory.** A fresh app needs one-time setup: `npx --yes eas-cli@latest init` to create\u002Flink the project (when there's no `projectId`), and **set `ios.bundleIdentifier`** in app config if it's missing — a fresh `create-expo-app` often has none, and `prebuild`\u002F`eas build` need it (they prompt or fail without it; e.g. `dev.\u003Cowner>.\u003Cslug>`). Read current config with `npx expo config --json` (it may live in `app.config.js`). The first Mode-C run is slow (native build); later runs reuse it.\n- A controller to drive the device. This skill uses **agent-device** (open source, MIT), run on demand via `npx agent-device@latest` — nothing globally installed. **argent** is an alternative (`--type argent` in `simulator:start`); see [references\u002Fcontrollers.md](.\u002Freferences\u002Fcontrollers.md).\n- **`.env.eas-simulator`** is written\u002Fmanaged by eas-cli (not this skill): it holds the session id (`EAS_SIMULATOR_SESSION_ID`) + the daemon URL\u002F**token**, so `get`\u002F`stop`\u002F`exec` default to that session (usually **omit `--id`**; pass `--id \u003Cid>` to target another). It carries a **token → keep it gitignored** (eas-cli marks it \"do not commit\" but may not add the ignore rule, and a fresh app's `.gitignore` won't cover it — add `.env.eas-simulator` if missing).\n- `--max-duration-minutes` is paid-plan only; otherwise a default applies.\n\n## The core loop (always the same)\n\nA session is: **start → (install your app) → drive → stop.** `eas-cli` owns the *session*; the device *verbs* (open\u002Ftap\u002Fscreenshot) come from the controller, which `npx --yes eas-cli@latest simulator:exec` runs for you with the session's connection env loaded.\n\n```bash\n# 1. Start a session (boots the remote sim + agent-device daemon; writes .env.eas-simulator).\nprintf '# managed by eas-cli\\n' > .env.eas-simulator   # clear any stale session first\nnpx --yes eas-cli@latest simulator:start --platform ios --type agent-device --non-interactive\n#    Then confirm it's live: simulator:get --json → status IN_PROGRESS (bounded poll in run-your-app.md).\n\n# 2. Drive it through `exec` (loads the session env, then runs the command you give it).\n#    agent-device runs on demand via npx — nothing installed globally.\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest open \u003Capp-or-url> --platform ios\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest snapshot -i          # interactive UI tree → @e1, @e2 refs\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest press @e2            # tap a ref (NOTE: 'press', not 'tap')\nnpx --yes eas-cli@latest simulator:exec npx agent-device@latest screenshot .\u002Fshot.png\n\n# 3. Stop (ends billing; tears down the VM) and reset the dotenv. Omit --id to target the dotenv session.\nnpx --yes eas-cli@latest simulator:stop\nprintf '# managed by eas-cli\\n' > .env.eas-simulator\n```\n\nTo **watch** it live, hand the user the `webPreviewUrl` that `start` prints (an `--type agent-device` iOS session runs serve-sim alongside the daemon, so it emits one — agent control *and* a browser preview in one session; Android has no preview, and `--type serve-sim` is preview-only). **This URL is for the *user's* browser — you cannot open it for them, and it must never touch the sim:**\n- **\"Open it here\" (Cursor\u002FVS Code)** → print the URL on its own line and tell the user to open Simple Browser (`Cmd\u002FCtrl+Shift+P` → \"Simple Browser: Show\") and paste it. Then **stop**: do not shell out to a system browser or a Cursor\u002FVS Code URL handler, and do not ask \"did a tab appear?\" — you can't confirm it, the handoff is done.\n- **Never `open` the `webPreviewUrl` on the sim.** It's a browser preview, not a deep link and not an `agent-device open` argument; routing it to the device renders a browser-in-a-browser (a real past failure).\n- **Headless agent** (no display) → just return the URL as the deliverable.\n- **Keeping it alive for the user to drive** → bound it: start with `--max-duration-minutes N` so it auto-stops; tell them it bills until stopped and when it auto-stops; offer to reopen\u002Fextend when it ends. (This is the one case where \"stop right away\" doesn't apply; one-shot `screenshot`\u002F`get` runs still stop immediately.)\n\n`start` also prints a job-run URL.\n\n## Commands at a glance\n\n| Command | Purpose |\n|---|---|\n| `npx --yes eas-cli@latest simulator:start --platform ios\\|android [--type agent-device\\|argent\\|serve-sim] [--package-version X] [--max-duration-minutes N] [--non-interactive] [--json]` | Create a session; boot the sim + controller; write `.env.eas-simulator`; print `webPreviewUrl` + job-run URL |\n| `npx --yes eas-cli@latest simulator:exec \u003Ccmd> [args…]` | Load `.env.eas-simulator`, then run `\u003Ccmd>` with that env. The bridge to the controller. |\n| `npx --yes eas-cli@latest simulator:get [--id] [--json]` | Session status + connection details. **Use this to confirm readiness** (see *Operating principles*). |\n| `npx --yes eas-cli@latest simulator:list [--status …] [--type …] [--platform …]` | List an app's sessions |\n| `npx --yes eas-cli@latest simulator:stop [--id]` | Stop a session (idempotent) |\n\n## Running the user's app — pick a mode\n\nThe remote sim boots **blank — no Expo Go, no apps.** Install a build, then drive it — but **match the build *type* to the goal first** (the box below); that's where live-session runs derail. Full sequences: [references\u002Frun-your-app.md](.\u002Freferences\u002Frun-your-app.md) — read before running a mode.\n\n> **Match the build to the goal before installing anything — this is where live-session runs derail.** Two traps, same root (grabbing a build that doesn't fit the request):\n> 1. **Wrong type.** Live edits (Mode C) **require a dev build.** A *static* build — a local Release (A), the default EAS sim build (B), or **any build left on the sim from an earlier screenshot run** — freezes its JS at build time and **can never hot-reload.** For a live request, **ignore existing builds entirely** and install a **dev** build (local Debug, or an EAS build with `developmentClient: true`). Never reconnect Metro to a static build hoping it'll reload — it won't.\n> 2. **Stale.** A static look must match current source — reuse only a fingerprint-matched build, else build fresh; reuse is explicit-only.\n>\n> So a leftover EAS\u002Frelease build is **not** a shortcut for \"iterate live\" — it's the wrong binary. The fact that a build *exists* never makes it the right one.\n\n| Mode | What it is | Choose when | Live edits? |\n|---|---|---|---|\n| **A — Local release build** | Build a Release `.app` locally, `agent-device install` it (uploads) | User has a Mac toolchain and wants a quick \"run my current code on a cloud device\" | No (rebuild to see changes) |\n| **B — EAS build** (rare, explicit-only) | `eas build` a simulator build, `agent-device install-from-source \u003Curl>` (the VM downloads it) | **Only when explicitly asked** — the user names an existing\u002FEAS build, or wants a static EAS artifact for CI\u002Fsharing. Not for \"show me\"\u002F\"iterate\" (use C). Sim builds need no credentials. | No |\n| **C — Local dev build + tunnel** | Dev (Debug) build + `EXPO_UNSTABLE_TUNNEL_V2=1 expo start --tunnel` + connect the dev client to Metro | **The agentic edit-and-see loop** — change code and see it live (Fast Refresh) | **Yes** |\n\nQuick decision — **default to C; A and B are explicit-only:**\n- **C (almost everything):** iterate, interact, poke the app, live edits — *and* most \"show me my app\" (current code needs a build anyway, so live+current wins). Mac → dev client builds locally; no Mac → build it on EAS (`developmentClient: true`). **Unsure → C.**\n- **A:** only an explicit one-shot **static** screenshot on a Mac.\n- **B:** only when the user names an existing\u002FEAS build or wants a static EAS artifact (CI\u002Fsharing) — see the box above for why a static build is the wrong tool for \"iterate.\"\n\n## Driving the device (agent-device)\n\n`agent-device` is the controller. Common verbs (run each as `npx --yes eas-cli@latest simulator:exec npx agent-device@latest \u003Cverb>`):\n\n| Verb | Does |\n|---|---|\n| `apps --platform ios` | List installed apps (the blank sim shows none) |\n| `install \u003CappId> \u003Cpath> --platform ios` | Install a local `.app` (uploads it) |\n| `install-from-source \u003Curl> --platform ios` | Install from a URL — the VM downloads it (use for EAS artifacts) |\n| `open \u003CappId\\|deep-link> --platform ios` | Launch an app (bundle id) or follow an app **deep link** (`exp+slug:\u002F\u002F…`). **Not** for the `webPreviewUrl` — that's a browser preview for the user, never the device. |\n| `snapshot -i` | Interactive accessibility tree → `@e1`-style refs |\n| `press \u003Cref\\|selector>` | Tap (e.g. `press @e2` or `press 'label=\"Open\"'`) — **the tap verb is `press`, not `tap`** |\n| `fill \u003Cref> \"text\"` | Type into a field |\n| `screenshot \u003Cpath>` | Capture the screen to a local PNG (downloaded from the daemon) — requires an app to be open (`open` first) |\n| `metro prepare` \u002F `metro reload` | Point a dev client at Metro \u002F reload (Mode C) |\n\nFor the full verb set and the `argent` controller alternative, see [references\u002Fcontrollers.md](.\u002Freferences\u002Fcontrollers.md).\n\n## Operating principles\n\nThe non-obvious mental model worth internalizing. Specific error→fix lookups (hung verbs, `tap`→`press`, `--platform`, `--json`, `pod install` locale, orphaned sessions, boot variability) live in [references\u002Ftroubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md).\n\n1. **Establish ground truth, then reset — don't patch-loop.** Never assume an existing session or Metro is yours or healthy. Before driving, confirm:\n   - **cwd** — you're in the intended Expo project dir (a misdirected `start`\u002F`exec` sessions the *wrong app* + drops a stray `.env.eas-simulator`; `pwd` \u002F check `app.json`).\n   - **session live** — `IN_PROGRESS` via `simulator:get --json` (a stopped session keeps its id + `remoteConfig`, so the dotenv alone isn't proof).\n   - **one Metro on `:8081`** — reuse if it's yours, else free the port before starting (run-your-app.md).\n   - **build fits intent** — a **release build can't live-reload**; if live edits are wanted and a release build is installed, **install the dev build, don't reconnect**.\n\n   If current code isn't rendering after your **first** connect, stop poking live state: **reset to baseline** (stop session → clear dotenv → kill Metro) and redo the mode **once**; a second failure → stop and report. Never restart Metro in place, reconnect more than once, rebuild the native client to fix a JS\u002Fconnection problem, or surface a preview URL while state is unknown. (A daemon drop — `ERR_NGROK_3200` \u002F `Remote daemon is unavailable` — is the same: reset, don't retry.)\n2. **`exec` is a wrapper, not a driver.** `simulator:exec` loads `.env.eas-simulator` and spawns the command you pass; the device verbs come from the controller (`npx agent-device@latest`). There is no `simulator:tap`.\n3. **Act immediately; don't park an idle session.** Sessions are short-lived — install and drive right after `start`. Leaving one idle drops the tunnel\u002Fdaemon (→ reset, per #1).\n4. **Stop on every exit path (billing) and reset the dotenv.** `--non-interactive` doesn't auto-stop, and a forgotten session bills until stopped. Don't `start` again to \"retry\" a slow boot — that orphans a second billed session.\n5. **Screenshot only the correct, fresh build.** Mode C only after the dev client connects to Metro; A\u002FB only from a build matching current source — reusing a pre-existing build is the #1 \"my edits don't show\" cause (see the build caveat above). (`9:41` in the status bar is the sim default, not staleness.)\n\n## Stop and clean up\n\nStop the session (ends billing) **and reset the dotenv** so a later run doesn't try to reuse the dead session:\n\n```bash\nnpx --yes eas-cli@latest simulator:stop          # omit --id → stops the dotenv session (or pass --id \u003Cid>)\nprintf '# managed by eas-cli\\n' > .env.eas-simulator   # clear the stale session id so it isn't reused\n# if you started Metro for Mode C, stop it too (Ctrl+C in its terminal, or kill the expo process)\n```\n\n## References\n\n- [references\u002Frun-your-app.md](.\u002Freferences\u002Frun-your-app.md) — full tested command sequences for modes A, B, and C (read before running a mode).\n- [references\u002Fcontrollers.md](.\u002Freferences\u002Fcontrollers.md) — agent-device verb reference and the `argent` alternative.\n- [references\u002Ftroubleshooting.md](.\u002Freferences\u002Ftroubleshooting.md) — concrete errors and fixes.\n\nSource of truth: Expo docs and the `eas` \u002F `agent-device` CLIs (`npx --yes eas-cli@latest simulator:* --help`, `agent-device --help`). This skill teaches how to apply them; it doesn't replace them.\n",{"name":5,"license":15,"version":49,"description":7,"allowed-tools":50},"1.0.0","Bash(npx *eas-cli@*), Bash(npx *agent-device@*), Bash(npx expo *), Bash(eas *), Bash(expo *), Bash(xcodebuild*), Bash(pod*)","claude\u002Finstall-gsd-build-foQdV","d86cd127f527124b5fd0fd0bc679a4d79b7d01d7",".agents\u002Fskills\u002Feas-simulator","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik","https:\u002F\u002Fnorvik-orpin.vercel.app","https:\u002F\u002Fgithub.com\u002Fpattanation","2026-07-17 11:17:04",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add pattanation\u002FNorvik --skill eas-simulator",{"tool":64,"command":65},"bunx","bunx skills add pattanation\u002FNorvik --skill eas-simulator",{"tool":67,"command":68},"pnpm","pnpm dlx skills add pattanation\u002FNorvik --skill eas-simulator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Feas-simulator\u002FSKILL.md",true,[72,78,82,86],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"agents\u002Fopenai.yaml","REFERENCE","参考文档",444,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Feas-simulator\u002Fagents\u002Fopenai.yaml",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcontrollers.md",4077,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Feas-simulator\u002Freferences\u002Fcontrollers.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Frun-your-app.md",12364,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Feas-simulator\u002Freferences\u002Frun-your-app.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Ftroubleshooting.md",6870,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Feas-simulator\u002Freferences\u002Ftroubleshooting.md",[91,122,148,171,193,208],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":105,"publishedAt":121},"01M71QDV4DM8T19HEHWATEF1K4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[99,102],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[106,107,108,109,110,36,111,112,113,114,27,115,116,117,118,119,120],"webapp","testing","webapp testing","for","applications","frontend","debugging","toolkit","logs","with","playwright","web","behavior","ui","screenshots","2026-11-10 13:02:02",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":121},"01M71QDH2GGMXGA9105C9W1N7B","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[129],{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[131,132,133,117,134,135,136,109,137,138,111,139,140,141,142,143,144,145,146,147],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","use","file","components","react","multi","state","routing","state management",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":121},"01M71QD9T2XC3EWMQNN9ACNWQ1","vueuse-functions","Apply VueUse composables where appropriate to build concise, maintainable Vue.js \u002F Nuxt features.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvueuse-functions\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvueuse-functions\u002FSKILL.md",[155],{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,161,162,163,164,165,166,167,168,169,170],"functions","vueuse","vueuse functions","project","nuxt","apply","github","concise","build","https","features","vue","js","composables",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":180,"publishedAt":121},"01M71QD51HWSGYMCMB7RW7PGK8","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-testing-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-testing-best-practices\u002FSKILL.md",[178,179],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[181,107,182,168,183,116,184,185,186,163,187,109,188,189,190,140,191,169,192],"vue testing best practices","testing best practices","best practices","test","testing patterns","component","vitest","mocking","e2e","utils","patterns","e2e testing",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":121},"01M71QD358H2DJ9THJRBP77T3T","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-router-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-router-best-practices\u002FSKILL.md",[200],{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[202,168,203,183,204,186,205,163,191,206,207],"router","vue router best practices","route","guards","navigation","lifecycle",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":212,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":121},"01M71QCYPNWDE2MQZ1TF3ED5S4","vue-best-practices","MUST be used for Vue.js tasks. Strongly recommends Composition API with `\u003Cscript setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-best-practices\u002FSKILL.md",[215],{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},[217,168,183,218,160,219,220,28,202,221,222,223,224,225,226,109,227,140,228,229],"vue best practices","Composition","files","tasks","pinia","work","options","ssr","typescript","as","vite","load","standard"]