android-emulator-harne…
Bring up an Android app in a headless emulator on Linux/WSL and drive it for automated integration testing, the Android analog of…
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
Claude Code
$ npx -y skills add simiancraft/simiancraft-skills --skill expo-developer-tools --agent claude-code
Codex
$ npx skills add simiancraft/simiancraft-skills --skill expo-developer-tools -a codex -y
Cursor
$ npx skills add simiancraft/simiancraft-skills --skill expo-developer-tools -a cursor -y
Gemini CLI
$ npx skills add simiancraft/simiancraft-skills --skill expo-developer-tools -a gemini-cli -y
GitHub Copilot
$ npx skills add simiancraft/simiancraft-skills --skill expo-developer-tools -a github-copilot -y
OpenCode
$ npx skills add simiancraft/simiancraft-skills --skill expo-developer-tools -a opencode -y
Windsurf
$ npx skills add simiancraft/simiancraft-skills --skill expo-developer-tools -a windsurf -y
name: expo-developer-tools description: >- 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". status: complete sources: - https://docs.expo.dev/debugging/tools/ (the developer menu and the tools it opens) - https://reactnative.dev/docs/react-native-devtools (the React Native DevTools panels) - https://www.rozenite.dev/ (Rozenite, the React Native DevTools plugin framework)
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.
1. `references/opening.md`: the open-gesture matrix (the one platform-divergent thing). 2. `references/dev-menu.md`: the developer-menu items, top to bottom as the app presents them. 3. `references/react-native-devtools.md`: the panels behind "Open DevTools". 4. `references/rozenite.md`: Rozenite plugins, the escape hatch when a built-in panel is not enough. 5. `references/techniques.md`: cross-tool techniques (named after the technique), at the bottom.
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.
Claude Code skills for the full arc of a change: farm to table, with receipts. Curated Claude Code skills and agents from simiancraft. Most skill collections are grab bags. This one has a spine: it carries a change through its whole life.
Bring up an Android app in a headless emulator on Linux/WSL and drive it for automated integration testing, the Android analog of…
Specialization of android-emulator-harness for CAMERA / segmentation testing: get a real PERSON in front of the emulator camera…
Appraise a GitHub issue backlog unattended: for each issue, decide whether it is still real and how big it is, then apply the…
Shrink a media asset to the smallest bytes that still serve its purpose, keyed on asset kind (raster, vector, animation, video,…
Run an unattended burndown of a GitHub issue backlog as cards on a per-operator GitHub Projects board whose lanes are an explicit…
Break one GitHub issue that is too large to work into sub-issues, unattended, and keep the carving honest as the children close.…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.