expo-ios-simulator
Skill8 starsChanged 5 months agoMITView on GitHub
Run and drive an Expo / React Native app on the iOS Simulator. Pick an execution mode (Expo Go, dev client, Storybook-mobile, web-on-mobile), build and install a dev client, and clear the recurring Expo/RN prompts that block automation: the push-token alert that stacks until the overlay darkens the screen, the "Open in app?" deep-link dialog, the dev menu, and the element-inspector trap. Sits ON TOP of ios-simulator; failures route to ios-simulator-triage. Project-agnostic; discovers bundle id and scheme from the app config. Use for "run my Expo app on the simulator", "load a dev client", or "drive Storybook on iOS".
- Installs packages
In this repository23 other files it gives its agents.
- skills/asset-optimization/AGENTS.mdAGENTS.md
- android-emulator-harnessSkill
- android-emulator-mask-testingSkill
- appraise-github-issuesSkill
- asset-optimizationSkill
- burn-down-github-issuesSkill
- carve-github-issueSkill
- code-github-issueSkill
- emoji-readoutSkill
- expo-developer-toolsSkill
- fix-github-issueSkill
- how-to-planSkill
- ios-simulator-flow-evidenceSkill
- ios-simulatorSkill
- ios-simulator-triageSkill
- mobile-accessibilitySkill
- playwright-camera-mask-testingSkill
- playwright-gif-captureSkill
- playwright-harnessSkill
- playwright-storybook-flowsSkill
- prove-github-issueSkill
- prove-work-on-githubSkill
- zone-composerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Every factual claim here and in the references cites a primary source (Expo, Apple, AXe's own help).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Expo on the iOS Simulator (layer on top of ios-simulator)
Everything here is Expo / React-Native runtime behavior, not the simulator itself (that is ios-simulator, which boots devices, captures screenshots, and grants permissions). This skill gets an Expo app running on a booted simulator and clears the Expo-specific overlays that stall automation. For "make the app driveable" see mobile-accessibility.
Before anything
A booted simulator and AXe installed; that is ios-simulator prerequisites.md. This
skill discovers everything app-specific (bundle id, scheme) from the app config; it never
hardcodes a project's nouns.
The loop
- Pick an execution mode (
references/execution-modes.md): Expo Go, a development build (dev client), Storybook-mobile, or web-on-mobile. The choice is forced by whether the app has custom native code. - Get the app on the device. Pure-JS app: Expo Go installs and launches it for you
(
references/expo-go.md). Anything with native modules or a config plugin: build and install a dev client (references/development-builds.md), then serve Metro and connect by deep link. - Clear the recurring prompts (
references/known-prompts.md): the "Open in app?" deep-link dialog, the push-token alert that re-fires and stacks on each reload, and the dev menu; avoid the element-inspector trap. Clear each by accessibility, never coordinates. - Drive it. The driving primitive is ios-simulator
references/driving.md(axe tap --id/--label); what makes the app addressable is mobile-accessibility.
Rules
- Discover bundle id and scheme from the app config; never hardcode them.
- Never drive a bundling app. Two readiness gates sit between "launched" and "driveable":
Metro serving (
curl /status) and the first bundle finishing (the tree grows labels); both recipes are inreferences/development-builds.md. Taps dispatched before them report success and do nothing. - Clear every Expo dialog and overlay by accessibility (
axe tap --label), not coordinates. - Every factual claim here and in the references cites a primary source (Expo, Apple, AXe's own help); a prior-art skill is never a source.
Out of scope
- The simulator itself, its chrome, capture, and permissions: ios-simulator.
- What makes an app addressable (accessibility props): mobile-accessibility.
- The dev menu's items and React Native DevTools (shared with Android): expo-developer-tools.
- Build, runtime, and automation failures: ios-simulator-triage.
References
references/execution-modes.md: the four ways to run an Expo app and when to use each.references/expo-go.md: the Expo Go path and its fixed-native-set limit.references/development-builds.md: building and connecting a dev client.references/known-prompts.md: the recurring dialogs, the dev menu, and the inspector trap.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

