expo-developer-tools
Skill8 starsChanged 5 months agoMITView on GitHub
Read and use the Expo / React Native in-app developer tools: the developer menu (reload, go home, performance monitor, element inspector, Open DevTools, and fast refresh) and React Native DevTools (Console, Sources, Network, Memory, Performance, Components, and Profiler), plus Rozenite plugins. The tools are identical on iOS and Android; only the gesture that opens the menu differs, so this skill is the shared home referenced by both the iOS-simulator and Android-emulator skills. This is the reference for reading these tools (what each shows and how to interpret it), not a driver. Use for "open the Expo dev menu", "read the performance monitor", "use the element inspector", or "inspect a component / a slow re-render with React Native DevTools".
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-ios-simulatorSkill
- 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
Files
Expo Developer Tools (shared iOS + Android)
The in-app developer tooling of an Expo / React Native app: the developer menu and the React Native DevTools it opens. This surface is a React Native feature, so it is the same on iOS and Android; the only platform-divergent part is the gesture that opens the menu. That is why this is a shared skill: ios-simulator / expo-ios-simulator and android-emulator-harness each say how to open the menu on their platform, then point here for what the items and panels mean.
This skill is the interpretive field guide: what each tool shows and how an agent reads it. It is not a driver; driving the app lives in the platform simulator/emulator skills.
Layout (in the order you meet the tools)
references/opening.md: the open-gesture matrix (the one platform-divergent thing).references/dev-menu.md: the developer-menu items, top to bottom as the app presents them.references/react-native-devtools.md: the panels behind "Open DevTools".references/rozenite.md: Rozenite plugins, the escape hatch when a built-in panel is not enough.references/techniques.md: cross-tool techniques (named after the technique), at the bottom.
Out of scope
Driving the app (tapping, typing, screenshots) -> the platform skills. Web debugging (Chrome DevTools, Playwright) -> the web skills; the web diverges from this mobile menu entirely.
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.