ワンクリックでManusで任意のスキルを実行

expo-developer-tools

スター6

フォーク0

更新日2026年7月1日 20:11

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".

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

simiancraft

simiancraft/simiancraft-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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.

このリポジトリの他の Skills

同じリポジトリ

asset-optimization

simiancraft/simiancraft-skills

Shrink a media asset to the smallest bytes that still serve its purpose, keyed on asset kind (raster, vector, animation, video, audio, model, document, font) and on where it will be presented. Detects and acquires the right binary from a central tool manifest, runs a lossless-or-lossy pass decided by fidelity intent, measures before and after, validates the output, and keeps the result only if it is smaller AND still valid, redirecting to a better format or a different kind when the source is wrong for the job (a no-alpha PNG-24 wants JPEG or WebP; an over-long GIF wants video). Optimizes one file or walks a whole repository. Use for "optimize/compress this image, gif, svg, video, audio, 3D model, or web font", "shrink a PNG", "which format should this asset be", or "make these assets smaller". Skip when the asset is already minimal, when the bytes must stay bit-exact for a reason other than size, or when a build-time plugin (a bundler image loader, expo-optimize) already optimizes it in the pipeline.

2026-07-026

ios-simulator

simiancraft/simiancraft-skills

Drive an iOS Simulator headlessly on macOS: discover and boot a device, install and launch an app, drive its UI by accessibility (AXe) rather than brittle coordinates, capture screenshots, and navigate the simulator's own chrome, menus, and execution modes. The iOS analog of android-emulator-harness and playwright-harness. Project-agnostic core; Expo/React-Native specifics live in expo-ios-simulator, and "make the app driveable" lives in mobile-accessibility. Use for any task that is "boot/run an iOS simulator", "drive an iOS screen", "screenshot the simulator", or "automate an iOS flow".

2026-07-016

expo-ios-simulator

simiancraft/simiancraft-skills

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".

2026-07-016

ios-simulator-triage

simiancraft/simiancraft-skills

Diagnose and recover from failures when building, running, or driving an app on the iOS Simulator. A living catalog organized by layer: build failures (xcodebuild, CocoaPods, signing, codegen), runtime failures split into app-runtime vs Expo-runtime (the red error overlay), and automation failures that emit no error (element not found in the accessibility tree, stuck flow). Each layer names where its logs live. Used alongside ios-simulator and expo-ios-simulator when something breaks. Project-agnostic.

2026-07-016

ios-simulator-flow-evidence

simiancraft/simiancraft-skills

Capture proof of a driven iOS-simulator flow: vision-verifiable screenshots, video (mp4), and a manifest tying steps to artifacts, plus an honest list of what a simulator cannot do (deliver a push, use a real camera, place a call, fully observe the network). Produces artifacts to a contract that a separate GitHub-presentation skill consumes; this skill owns extraction, not publishing. Sits beside ios-simulator; project-agnostic. Use for "capture evidence of an iOS flow" or "record the simulator".

2026-07-016

mobile-accessibility

simiancraft/simiancraft-skills

2026-07-016

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)"]

Expo Developer Tools (shared iOS + Android)

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.