メニュー
Use this skill when inspecting, launching, logging, clicking, typing, or selecting context from Electron apps through ADE App Control and the `ade app-control` CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Autonomous PR-to-merge loop. Polls CI and review bots, fixes failures, rebases only on real conflicts, and lands the PR on main. Soft cap of 5 normal iterations plus one force-finalize iteration that bypasses review and fixes only CI. Pure loop — it does NOT run /quality or /test; run those first. Full phase logic lives in docs/playbooks/ship-lane.md.
ADE release conductor: detect whether desktop and/or iOS actually changed, bump desktop patch versions, keep iOS marketing versions fixed while bumping build numbers, ship desktop through the GitHub Actions release workflow, and distribute TestFlight builds to all beta users.
Use this skill when an agent needs to inspect or operate ADE itself through the `ade` CLI, including lanes, chats, actions, proof, runtime/socket state, or help/flag discovery.
Use this skill when creating, inspecting, syncing, committing, pushing, archiving, or rebasing ADE lanes and lane worktrees through `ade lanes` and `ade git`.
Use this skill when using ADE's built-in browser pane, shared browser tabs, screenshots, page inspection, or browser context selection through `ade browser`.
Prove the new code works: enforce the logging/PostHog ground truth, prune dead tests, consolidate fragments, add only tests that prove new contracts, turn each /quality Blocker/High finding into a named regression test, then run CI-mirrored shards. Also keeps docs/mobile/CLI/TUI parity in lockstep.
| name | ade-app-control |
| description | Use this skill when inspecting, launching, logging, clicking, typing, or selecting context from Electron apps through ADE App Control and the `ade app-control` CLI. |
App Control is a live desktop drawer service. Prefer socket-backed commands:
ade help app-control
ade --socket app-control status --text
ade --socket app-control claim --lane <lane-id> --text
ade --socket app-control launch --command "npm run dev" --text
ade --socket app-control connect --cdp-port <port> --text
ADE sets ADE_APP_CONTROL_CDP_PORT and ADE_APP_CONTROL_DEBUG_FLAGS for launches. Custom Electron launchers should forward one of those values to --remote-debugging-port.
ADE-launched agents pass ADE_LANE_ID / ADE_CHAT_SESSION_ID through launch, connect, and claim; use claim when attaching to a renderer that is already running so the Work tools pane attributes it to the agent's lane instead of the visible chat.
ade --socket app-control snapshot --text
ade --socket app-control elements --text
ade --socket app-control select --x <x> --y <y> --text
Use Inspect mode or select to return screenshot-backed DOM, selector, and source context. When the session is owned by a chat or tracked CLI session, ADE can attach the selection to that active Work surface.
ade --socket app-control click --x <x> --y <y> --text
ade --socket app-control type --value "text" --text
Use Control mode for input. Re-snapshot after meaningful UI changes.
Start with App Control status, then prefer App Control terminal/log commands:
ade --socket app-control logs --text --max-bytes 8388608
ade --socket app-control terminal write --data "y\n"
ade --socket app-control terminal signal --signal SIGINT
Only fall back to ade --socket terminal list --text and ade --socket terminal read ... when no App Control terminal is active.
If you are an agent running inside one ADE instance (e.g. ADE Beta or stable) and you need to launch the ADE dev desktop app under App Control, the dev launcher is already isolated and safe to run:
ade --socket app-control launch --command "npm run dev" --text
npm run dev uses its own runtime socket (/tmp/ade-runtime-dev.sock) and a separate Electron profile (ade-desktop-dev), so it will not collide with the runtime/socket that is hosting you. Confirm with ade runtime status --text before launching — that tells you which socket the CLI is currently attached to.
npm run dev watches apps/desktop/src/main/** and restarts Electron whenever the main bundle rebuilds. After a restart, the App Control drawer UI in the parent ADE window can show stale Waiting for CDP on 127.0.0.1:<port> even though the new renderer is already exposed on the same port. From the CLI you can confirm and re-bind:
ade --socket app-control targets --text # find the new page target id
ade --socket app-control attach-target --target <id> --text
ade --socket app-control snapshot --text # forces the drawer to repaint
If targets shows a /devtools/page/<id> entry with the dev URL (http://localhost:5173/...), CDP is healthy — the drawer banner is just lagging until the next snapshot.