菜单
Enable FlutterHelm runtime_interaction beta with the built-in external runtime driver and optional mobile-mcp companion MCP. Use when Codex needs semantic tap, text entry, scroll, richer screenshots, or UI-state verification on a running Flutter session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | flutterhelm-beta-runtime-interaction |
| description | Enable FlutterHelm runtime_interaction beta with the built-in external runtime driver and optional mobile-mcp companion MCP. Use when Codex needs semantic tap, text entry, scroll, richer screenshots, or UI-state verification on a running Flutter session. |
Use this skill only when the user explicitly wants beta UI interaction behavior.
runtime_interaction workflow in FlutterHelm config.runtimeDriver provider.session://<id>/health for:
runtimeInteractionReadyscreenshotReadydriverConnectedsupportedLocatorFieldscapture_screenshot first, then tap_widget, enter_text, and scroll_until_visible.mobile-mcp setup opt-in. The default plugin .mcp.json does not start it.references/mobile-mcp-setup.md for the beta config, optional companion MCP entry, and expected health fields.../../../../docs/11-user-guide.md for the repo's full runtime_interaction guide.Guide stable FlutterHelm setup and execution through the default npx-backed plugin workflow. Use when Codex needs to start or operate stable FlutterHelm flows such as workspace selection, run and inspect, tests, profiling, compatibility checks, or native handoff without enabling beta runtime_interaction or native_build paths.
Configure and use FlutterHelm native_build beta with a stdio_json nativeBuild provider such as an XcodeBuildMCP-like backend. Use when Codex needs iOS-first native build or launch plus same-session Flutter runtime attachment and correlated native evidence.
Diagnose FlutterHelm failures and degraded states. Use when Codex needs to triage approval_required responses, SESSION_BUSY or WORKSPACE_BUSY, root or fallback problems, degraded delegate/provider health, runtime driver errors, native_build setup problems, or HTTP preview confusion.