Expo developer tools
Skill simiancraft/simiancraft-skills/skills/expo-developer-tools
Public Claude Code skills and agents from simiancraft. Marketplace-installable.
npx -y skills add simiancraft/simiancraft-skills --skill expo-developer-toolsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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".
SKILL.md
2.5 KB, as published. Nobody here has run it
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.