@bdayadev/flutter-ultra-mcp 1.5.8 → 1.7.0

package/skills/devtools/SKILL.md

@@ -1,131 +1,133 @@
 ---
 name: flutter-devtools
-description: Wiring up and using the flutter-ultra DevTools panel to inspect live MCP activity, attached sessions, and agent tool calls from inside the IDE. Use when the user wants to see the plugin's activity timeline, pause/resume agent flows from the panel, or stream screenshots to the DevTools view.
+description: Wires up and uses the flutter-ultra DevTools panel to inspect live MCP activity, pause/resume agent flows, and stream screenshots to the DevTools view. Use when the user wants to see plugin activity in DevTools, set up human-in-the-loop review gates, or stream live progress from tours and drive flows.
 ---
 
-# flutter-devtools — Wire Up the DevTools Panel
+# DevTools Panel Integration
 
-## When to use
+## Workflow
 
-Use this skill when the user wants to:
+### 1. Ensure `ultra_flutter_devtools` is in dev_dependencies
 
-- See live MCP tool call activity inside Flutter DevTools while the agent is running.
-- Pause or resume an automated agent flow from a panel button (human-in-the-loop).
-- Stream screenshots or session events to the DevTools view during a tour or drive flow.
-- Verify that the DevTools extension is correctly wired to the running MCP server.
+- `mcp__plugin_flutter_flutter-ultra-build__project_info` to check existing dependencies.
+- If missing: `mcp__plugin_flutter_flutter-ultra-build__pub_add` with `ultra_flutter_devtools`, `dev: true`.
+- If `pub_add` fails (bundled package): `mcp__plugin_flutter_flutter-ultra-build__pubspec_overrides_set` with the bundled path, then `mcp__plugin_flutter_flutter-ultra-build__pub_get`.
 
-## Prerequisites
+### 2. Start the panel server
 
-- The flutter-ultra-mcp plugin is already set up in the project (run `/flutter-setup` first if not).
-- Flutter DevTools is open in the IDE (VS Code: `Dart: Open DevTools` from the command palette; Android Studio: via the Flutter Inspector toolbar).
-- The DevTools extension tab labeled **flutter-ultra** must be visible. If it is not, the `ultra_flutter_devtools` package may not be in `dev_dependencies` — step 1 covers this.
+- `mcp__plugin_flutter_flutter-ultra-devtools__start_panel_server` with `port: 9170`.
+- Returns `{ url, port, status }`.
+- If port is in use, call `mcp__plugin_flutter_flutter-ultra-devtools__panel_status` first — if already running, skip to step 3.
 
-## Workflow
+### 3. Verify connection
 
-### 1. Ensure `ultra_flutter_devtools` is in dev_dependencies
+- Open Flutter DevTools in the IDE, navigate to the **flutter-ultra** tab.
+- `mcp__plugin_flutter_flutter-ultra-devtools__panel_status` — expect `{ running: true, viewers: 1 }`.
 
-- Call `mcp__plugin_flutter_flutter-ultra-build__project_info` to read existing dependencies.
-- If `ultra_flutter_devtools` is NOT listed under `dev_dependencies`:
-  - Call `mcp__plugin_flutter_flutter-ultra-build__pub_add` with `package: ultra_flutter_devtools`, `dev: true`.
-  - Call `mcp__plugin_flutter_flutter-ultra-build__pub_get` to resolve.
-- If `pub_add` fails (package not on pub.dev — it is bundled with the MCP plugin):
-  - Call `mcp__plugin_flutter_flutter-ultra-build__pubspec_overrides_set` with the bundled package path.
-  - Add `ultra_flutter_devtools: any` manually under `dev_dependencies` in `pubspec.yaml`.
-  - Call `mcp__plugin_flutter_flutter-ultra-build__pub_get`.
+### 4. Test the pipeline
 
-### 2. Start the panel WebSocket server
+- `mcp__plugin_flutter_flutter-ultra-devtools__push_event` with:
+  - `type: "custom"`, `server: "flutter-ultra-devtools"`, `payload: { message: "panel connected" }`.
+- If `delivered: 1`, the panel is receiving events.
 
-- Call `mcp__plugin_flutter_flutter-ultra-devtools__start_panel_server` with `port: 9170` (default).
-  - Returns: `{ url: "ws://127.0.0.1:9170", port: 9170, status: "listening" }`.
-  - If the port is already in use, retry with `port: 9171` (or any free port above 9170).
-- Note the returned `url` — this is what the DevTools extension iframe connects to.
+### 5. Stream activity during automated flows
 
-### 3. Connect the DevTools extension
+Push events to keep the panel updated during `/flutter:tour` or `/flutter:drive`:
 
-- Open Flutter DevTools in the IDE and navigate to the **flutter-ultra** tab.
-- The extension panel auto-connects to `ws://127.0.0.1:9170` when the tab loads (default port).
-- Verify connection by calling `mcp__plugin_flutter_flutter-ultra-devtools__panel_status`:
-  - Expect: `{ running: true, viewers: 1, url: "ws://127.0.0.1:9170" }`.
-  - If `viewers: 0` after 10 seconds, the extension has not connected — see edge cases below.
+**Screenshot events:**
+```
+push_event(type: "screenshot", payload: { path: "tour/login.png", route: "/login" })
+```
 
-### 4. Push a test event to confirm the pipeline
+**Tool result events:**
+```
+push_event(type: "tool_result", payload: { tool: "tap", status: "ok" })
+```
+
+**Error events:**
+```
+push_event(type: "error", payload: { message: "Widget not found" })
+```
 
-- Call `mcp__plugin_flutter_flutter-ultra-devtools__push_event` with:
-  - `type: "custom"`
-  - `server: "flutter-ultra-devtools"`
-  - `payload: { message: "flutter-ultra panel connected" }`
-- If `delivered: 1` is returned, the panel is receiving events. The user should see the notification in the DevTools flutter-ultra tab.
+Combine with tools from other servers for rich context:
 
-### 5. Stream activity during automated flows (optional)
+- After `mcp__plugin_flutter_flutter-ultra-runtime__screenshot`, push the path as a screenshot event.
+- After `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors`, push errors as error events.
+- After `mcp__plugin_flutter_flutter-ultra-gesture__tap`, push the result as a tool_result event.
+- After `mcp__plugin_flutter_flutter-ultra-patrol__get_patrol_result`, push test results.
 
-During long operations (tour, drive, patrol test runs), push events to keep the panel updated:
+### 6. Human-in-the-loop review gates
 
-- After each screenshot: call `push_event` with `type: "screenshot"` and `payload: { path: "<screenshot-path>", route: "<current-route>" }`.
-- After each tool call completes: call `push_event` with `type: "tool_result"` and `payload: { tool: "<tool-name>", status: "ok" }`.
-- On error: call `push_event` with `type: "error"` and `payload: { message: "<error>" }`.
+To pause and wait for the panel user to click Resume:
 
-This is especially useful when running `/flutter-tour` or `/flutter-drive` so the user can follow progress without reading the raw agent output.
+- `mcp__plugin_flutter_flutter-ultra-devtools__panel_command` with `timeoutMs` and `prompt`.
+- Returns `{ type: "resume" | "pause" | <custom>, payload, viewerId, timestamp }`.
+- `type === "pause"` means abort; `type === "resume"` means continue.
 
-### 6. Wait for human-in-the-loop panel commands (optional)
+Useful during:
 
-To pause an automated flow and wait for the panel user to click a button:
+- Long `flutter-tour` runs — let the user review each route before continuing.
+- `flutter-drive` validation flows — gate critical steps behind human approval.
+- `flutter-test` patrol runs — pause after failures for manual inspection.
 
-- Call `mcp__plugin_flutter_flutter-ultra-devtools__panel_command` with:
-  - `timeoutMs: 300000` (5 minutes — adjust to the expected review window)
-  - `prompt: "Review the current state and click Resume when ready."`
-- The tool blocks until the panel user sends a command or the timeout expires.
-- Returns: `{ type: "resume" | "pause" | <custom>, payload: {...}, viewerId: "...", timestamp: "..." }`.
-- Use `type === "pause"` to abort the current flow; `type === "resume"` to continue.
+### 7. Stop the server
 
-### 7. Stop the server when done
+- `mcp__plugin_flutter_flutter-ultra-devtools__stop_panel_server` when the session ends.
 
-- Call `mcp__plugin_flutter_flutter-ultra-devtools__stop_panel_server` when the session ends.
-  - This disconnects all panel viewers and frees the port.
-  - Safe to call even if no viewers are connected.
+## Edge cases
 
-## Handling edge cases
+- **`viewers: 0` after tab load**: the DevTools extension connects to port 9170 by default. If a different port was used, restart with 9170.
+- **Port already in use**: `mcp__plugin_flutter_flutter-ultra-devtools__panel_status` first — if running, reuse it.
+- **DevTools tab not visible**: `ultra_flutter_devtools` must be imported somewhere in the app (self-registers on import).
+- **`panel_command` times out**: treat as "continue" and proceed. Notify the user.
+- **Multiple DevTools windows**: `push_event` broadcasts to all. `panel_command` dequeues from the first responder.
 
-- **`viewers: 0` after tab load**: the DevTools extension connects to port 9170 by default. If `start_panel_server` used a different port, the extension won't find it. Either restart with port 9170, or check if the extension allows a custom port in its settings panel.
-- **Port already in use**: `start_panel_server` will throw. Call `panel_status` first — if `running: true` and the port matches, the server is already up from a previous session; skip to step 3.
-- **`pub_add ultra_flutter_devtools` fails**: the package is bundled inside the MCP plugin distribution. Ask the user for the plugin root path and use `pubspec_overrides_set` to point to `<plugin-root>/packages/flutter-ultra-devtools/dart/`.
-- **DevTools tab not visible**: the `ultra_flutter_devtools` package must be imported somewhere in the app (it self-registers its DevTools extension on import). Add `import 'package:ultra_flutter_devtools/ultra_flutter_devtools.dart';` to the entry point or a debug-only file.
-- **`panel_command` times out**: the panel user did not interact within `timeoutMs`. Treat the timeout as a "continue" signal and proceed with the automated flow. Notify the user in your response that the timeout elapsed.
-- **Multiple IDEs / DevTools windows**: each opened DevTools flutter-ultra tab creates a separate viewer. `push_event` broadcasts to all of them. `panel_command` dequeues from the first one that sends a response — subsequent responses from other viewers are discarded.
+## Tool reference
 
-## Output format
+| Action | Tool |
+|--------|------|
+| Start server | `mcp__plugin_flutter_flutter-ultra-devtools__start_panel_server` |
+| Stop server | `mcp__plugin_flutter_flutter-ultra-devtools__stop_panel_server` |
+| Check status | `mcp__plugin_flutter_flutter-ultra-devtools__panel_status` |
+| Push event | `mcp__plugin_flutter_flutter-ultra-devtools__push_event` |
+| Wait for command | `mcp__plugin_flutter_flutter-ultra-devtools__panel_command` |
+| Project info | `mcp__plugin_flutter_flutter-ultra-build__project_info` |
+| Add dependency | `mcp__plugin_flutter_flutter-ultra-build__pub_add` |
+| Resolve deps | `mcp__plugin_flutter_flutter-ultra-build__pub_get` |
+| Overrides set | `mcp__plugin_flutter_flutter-ultra-build__pubspec_overrides_set` |
+| VM screenshot | `mcp__plugin_flutter_flutter-ultra-runtime__screenshot` |
+| Runtime errors | `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors` |
+| Gesture tap | `mcp__plugin_flutter_flutter-ultra-gesture__tap` |
+| Patrol result | `mcp__plugin_flutter_flutter-ultra-patrol__get_patrol_result` |
 
-After completing setup, report:
+## Event types reference
 
-1. **Panel URL**: the WebSocket URL the extension connects to.
-2. **Viewer count**: how many DevTools windows are connected.
-3. **Test event delivered**: yes/no.
-4. **Next steps**: suggest running `/flutter-tour` or `/flutter-drive` with the panel open to see live event streaming.
+| Type | Payload | When to use |
+|------|---------|-------------|
+| `custom` | `{ message: string }` | General notifications |
+| `screenshot` | `{ path: string, route?: string }` | After capturing a screenshot |
+| `tool_result` | `{ tool: string, status: string }` | After any tool call completes |
+| `error` | `{ message: string, stack?: string }` | On runtime errors or tool failures |
+| `progress` | `{ step: number, total: number, label: string }` | During multi-step flows |
+| `test_result` | `{ name: string, passed: boolean }` | After each test completes |
 
 ## Example
 
 ```
-User: "Wire up the DevTools panel so I can see what the agent is doing."
-
-1. project_info → ultra_flutter_devtools not in dev_dependencies
-2. pub_add ultra_flutter_devtools dev:true → added
-3. pub_get → resolved
-4. start_panel_server port:9170 → url: ws://127.0.0.1:9170
-5. [User opens DevTools → flutter-ultra tab]
-6. panel_status → { running: true, viewers: 1 }
-7. push_event type:custom payload:{ message: "flutter-ultra panel connected" }
-   → delivered: 1
-8. Panel confirmed working.
-
-Panel URL: ws://127.0.0.1:9170 — 1 viewer connected.
-Test event delivered: yes.
-Next: run /flutter-tour with the panel open to see screenshots streaming live.
+User: "Wire up the DevTools panel."
+
+1. project_info -> ultra_flutter_devtools not in dev_dependencies
+2. pub_add ultra_flutter_devtools dev:true
+3. pub_get
+4. start_panel_server(port: 9170) -> ws://127.0.0.1:9170
+5. [User opens DevTools -> flutter-ultra tab]
+6. panel_status -> { running: true, viewers: 1 }
+7. push_event(type: "custom", payload: { message: "panel connected" }) -> delivered: 1
+-> "Panel at ws://127.0.0.1:9170, 1 viewer connected."
 ```
 
 ## See also
 
-- Sibling skill: `flutter-tour` — route screenshot tour; push screenshot events during the tour
-- Sibling skill: `flutter-drive` — multi-step flows; use `panel_command` for human review gates
-- `mcp__plugin_flutter_flutter-ultra-devtools__start_panel_server` — start the WS server
-- `mcp__plugin_flutter_flutter-ultra-devtools__panel_status` — check viewer count
-- `mcp__plugin_flutter_flutter-ultra-devtools__push_event` — stream events to the panel
-- `mcp__plugin_flutter_flutter-ultra-devtools__panel_command` — wait for human-in-the-loop input
+- `flutter-tour` — route screenshot tour; push screenshot events during the tour
+- `flutter-drive` — multi-step flows; use `panel_command` for human review gates
+- `flutter-test` — test orchestration; push test results to the panel

package/skills/drive/SKILL.md

@@ -1,143 +1,135 @@
 ---
 name: flutter-drive
-description: Driving multi-step user flows in a running Flutter app via gestures and assertions. Use when reproducing a bug across several screens, validating an onboarding flow, or running an ad-hoc end-to-end scenario without writing a patrol test.
+description: Drives multi-step user flows in a running Flutter app via gestures and assertions. Use when reproducing a bug across several screens, validating an onboarding flow, running an ad-hoc end-to-end scenario without writing a patrol test, or automating login/checkout/form-submission sequences.
 ---
 
-# flutter-drive — Multi-Step User Flow Automation
+# Multi-Step User Flow Automation
 
-## When to use
-
-Use this skill when the user wants to walk through a specific interactive flow — login sequences, checkout funnels, onboarding wizards, form submissions — and wants the agent to drive the app step by step, verifying state and capturing screenshots between major steps. This is ad-hoc flow automation; for repeatable E2E test suites use the `flutter-test` skill instead.
-
-## Prerequisites
-
-- A Flutter app is running in debug mode with the `ultra_flutter` binding initialized (or the app can be launched via `mcp__plugin_flutter_flutter-ultra-runtime__launch_app`).
-- The user has described the flow to execute (e.g. "log in as user@example.com, navigate to invoices, open the first one").
-- For web OAuth flows: a browser context must be available via `mcp__plugin_flutter_flutter-ultra-browser__launch_browser`.
+Drive interactive flows step by step — login sequences, checkout funnels, onboarding wizards, form submissions — verifying state and capturing screenshots between major steps. For repeatable E2E test suites, use `flutter-test` instead.
 
 ## Workflow
 
 ### 1. Attach to the running session
 
-- Call `mcp__plugin_flutter_flutter-ultra-runtime__discover_sessions` — pick the session matching the target app.
-- Call `mcp__plugin_flutter_flutter-ultra-runtime__attach` with `sessionId`.
-- Take an initial screenshot with `mcp__plugin_flutter_flutter-ultra-runtime__screenshot` to confirm starting state.
+- `mcp__plugin_flutter_flutter-ultra-runtime__discover_sessions` to find active sessions.
+- If none, `mcp__plugin_flutter_flutter-ultra-runtime__launch_app` + `mcp__plugin_flutter_flutter-ultra-runtime__poll_launch_app`.
+- `mcp__plugin_flutter_flutter-ultra-runtime__attach` with the chosen session.
+- `mcp__plugin_flutter_flutter-ultra-runtime__screenshot` to confirm starting state.
 
-### 2. Plan the flow steps
+### 2. Plan the flow
 
-Break the user's request into discrete, verifiable steps:
+Break the user's request into discrete, verifiable steps. Announce the plan before executing if more than 3 steps.
 
-```
-Step 1: Navigate to /login
-Step 2: Enter email "user@example.com" in field key='email-field'
-Step 3: Enter password in field key='password-field'
-Step 4: Tap button key='sign-in-button'
-Step 5: Verify dashboard loaded (widget key='dashboard-root' present)
-Step 6: Screenshot
-```
+### 3. For each step: inspect, act, verify, screenshot
 
-Announce the plan before executing if it involves more than 3 steps.
+**Inspect the current UI:**
 
-### 3. For each step — inspect → act → verify → screenshot
+- `mcp__plugin_flutter_flutter-ultra-runtime__find_widget` to confirm the target element exists.
+- `mcp__plugin_flutter_flutter-ultra-gesture__interactive_elements` to discover all tappable/editable elements on screen.
+- If not found, `mcp__plugin_flutter_flutter-ultra-runtime__get_widget_tree` to understand the hierarchy.
 
-**Inspect the current UI:**
+**Perform the action:**
 
-- Call `mcp__plugin_flutter_flutter-ultra-runtime__find_widget` with `key` or `text` to confirm the target element exists before acting.
-- If `find_widget` returns nothing, call `mcp__plugin_flutter_flutter-ultra-runtime__get_widget_tree` to understand the current widget hierarchy and adjust the finder.
+| Action | Tool |
+|--------|------|
+| Tap by key/text/coords | `mcp__plugin_flutter_flutter-ultra-gesture__tap` |
+| Double tap | `mcp__plugin_flutter_flutter-ultra-gesture__double_tap` |
+| Long press | `mcp__plugin_flutter_flutter-ultra-gesture__long_press` |
+| Enter text | `mcp__plugin_flutter_flutter-ultra-gesture__enter_text` |
+| Clear text field | `mcp__plugin_flutter_flutter-ultra-gesture__clear_text` |
+| Scroll to element | `mcp__plugin_flutter_flutter-ultra-gesture__scroll_to` |
+| Scroll until visible | `mcp__plugin_flutter_flutter-ultra-gesture__scroll_until_visible` |
+| Swipe gesture | `mcp__plugin_flutter_flutter-ultra-gesture__swipe` |
+| Pinch zoom | `mcp__plugin_flutter_flutter-ultra-gesture__pinch_zoom` |
+| Navigate programmatically | `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` |
 
-**Perform the action** (choose appropriate tool):
+**Wait for the UI to settle:**
 
-- **Tap by key**: `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` with `find.byKey(ValueKey('btn')).first.tap()` via the gesture VM extension, or use marionette's `mcp__marionette__tap` if connected.
-- **Enter text**: `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` to set controller value, or `mcp__marionette__enter_text` for native keyboard input.
-- **Scroll**: `mcp__marionette__scroll_to` with the target key.
-- **Navigate programmatically**: `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` with `context.go('/route')`.
+- `mcp__plugin_flutter_flutter-ultra-gesture__wait_for` to wait for a widget to appear/disappear after an action.
+- Or `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` with `SchedulerBinding.instance.endOfFrame`.
 
 **Verify the result:**
 
-- Call `mcp__plugin_flutter_flutter-ultra-runtime__find_widget` for an expected element on the next screen.
-- Or call `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` to read state: `MyBloc.of(context).state.runtimeType.toString()`.
-- If verification fails: call `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors` and `mcp__plugin_flutter_flutter-ultra-runtime__get_logs` before reporting failure.
+- `mcp__plugin_flutter_flutter-ultra-runtime__find_widget` for an expected element on the next screen.
+- `mcp__plugin_flutter_flutter-ultra-runtime__widget_exists` for quick existence checks.
+- `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` to read state: `MyBloc.of(context).state.runtimeType`.
+- On failure: `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors` and `mcp__plugin_flutter_flutter-ultra-runtime__get_logs`.
+
+**Screenshot after major transitions:**
+
+- `mcp__plugin_flutter_flutter-ultra-runtime__screenshot` for VM-level capture.
+
+### 4. HTTP/gRPC verification (optional)
 
-**Screenshot after major transitions** (not every micro-step):
+Capture network traffic during the flow to verify API calls:
 
-- `mcp__plugin_flutter_flutter-ultra-runtime__screenshot` → save to `.omc/research/drive-<date>/<step-N>-<label>.png`.
+- `mcp__plugin_flutter_flutter-ultra-runtime__start_http_capture` before starting the flow.
+- `mcp__plugin_flutter_flutter-ultra-runtime__get_http_events` at checkpoints to verify expected API calls were made.
+- `mcp__plugin_flutter_flutter-ultra-runtime__decode_grpc_message` to inspect gRPC request/response payloads.
+- `mcp__plugin_flutter_flutter-ultra-runtime__stop_http_capture` when done.
 
-### 4. Web OAuth / external popups (web target)
+### 5. Web OAuth / external popups (web targets)
 
 When a flow involves an external OAuth consent screen:
 
-1. Call `mcp__plugin_flutter_flutter-ultra-browser__intercept_redirect` to capture the redirect URL.
-2. Call `mcp__plugin_flutter_flutter-ultra-browser__navigate` to drive the external auth page.
-3. Call `mcp__plugin_flutter_flutter-ultra-browser__fill` for username/password fields.
-4. Call `mcp__plugin_flutter_flutter-ultra-browser__click` on the submit button.
-5. Call `mcp__plugin_flutter_flutter-ultra-browser__wait_for_url` matching the app's redirect URI.
-6. Re-attach to the Flutter runtime after the redirect completes.
+1. `mcp__plugin_flutter_flutter-ultra-browser__intercept_redirect` to capture the redirect URL.
+2. `mcp__plugin_flutter_flutter-ultra-browser__navigate` to drive the external auth page.
+3. `mcp__plugin_flutter_flutter-ultra-browser__fill` for username/password fields.
+4. `mcp__plugin_flutter_flutter-ultra-browser__click` on the submit button.
+5. `mcp__plugin_flutter_flutter-ultra-browser__wait_for_url` matching the app's redirect URI.
 
-### 5. Native mobile system dialogs (mobile target)
+### 6. Native mobile system dialogs (mobile targets)
 
-When the flow triggers OS-level permission dialogs or system sheets:
+- `mcp__plugin_flutter_flutter-ultra-native-mobile__wait_for_native_element` to detect OS dialogs.
+- `mcp__plugin_flutter_flutter-ultra-native-mobile__native_permission_grant` or `mcp__plugin_flutter_flutter-ultra-native-mobile__native_permission_deny`.
+- `mcp__plugin_flutter_flutter-ultra-native-mobile__native_tap` for other system UI elements.
+- `mcp__plugin_flutter_flutter-ultra-native-mobile__native_back` for Android back navigation.
+- `mcp__plugin_flutter_flutter-ultra-native-mobile__native_home` to press Home.
+- `mcp__plugin_flutter_flutter-ultra-native-mobile__solve_oauth_cct` for Chrome Custom Tab OAuth flows.
 
-- Call `mcp__plugin_flutter_flutter-ultra-native-mobile__wait_for_native_element` to detect the dialog.
-- Call `mcp__plugin_flutter_flutter-ultra-native-mobile__native_permission_grant` or `native_permission_deny`.
-- Call `mcp__plugin_flutter_flutter-ultra-native-mobile__native_tap` for other system buttons.
+### 7. Native desktop dialogs (desktop targets)
 
-### 6. Report the flow result
+- `mcp__plugin_flutter_flutter-ultra-native-desktop__wait_for_window` to detect native dialogs.
+- `mcp__plugin_flutter_flutter-ultra-native-desktop__desktop_click` to interact with dialog buttons.
+- `mcp__plugin_flutter_flutter-ultra-native-desktop__desktop_type` for text input in native fields.
+- `mcp__plugin_flutter_flutter-ultra-native-desktop__select_file_in_dialog` for file picker dialogs.
+- `mcp__plugin_flutter_flutter-ultra-native-desktop__confirm_dialog` to accept/dismiss confirmation dialogs.
 
-After all steps complete, produce:
+### 8. Report the flow result
 
-- A numbered summary of steps taken, each with pass/fail status and the screenshot path if captured.
-- Any errors encountered (with stack traces from `get_runtime_errors`).
-- Final state description (current route, visible widget).
+Produce a numbered summary: steps taken, pass/fail status per step, screenshot paths, and any errors from `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors`.
 
 ## Handling edge cases
 
-- **Element not found**: call `get_widget_tree` from the root to find where the element actually is; the app may still be loading or may have navigated differently than expected. Wait up to 3 seconds in 500 ms increments by calling `evaluate` with `SchedulerBinding.instance.endOfFrame`.
-- **App is on wrong route**: call `evaluate` with `GoRouter.of(context).routerDelegate.currentConfiguration.fullPath` to read current route, then navigate to the expected starting point.
-- **Text field requires focus first**: tap the field before entering text; use `find_widget` to confirm it has focus via `hasFocus` property.
-- **Async operations in progress**: check for loading indicators via `find_widget` with type `CircularProgressIndicator`; wait and retry.
-- **Hot-reload after code change**: call `mcp__plugin_flutter_flutter-ultra-runtime__hot_reload` after any code edit, then re-verify the widget tree before continuing.
-
-## Key tool reference
-
-| Action                        | Tool                                                                                                  |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------- |
-| Find element by key/text      | `mcp__plugin_flutter_flutter-ultra-runtime__find_widget`                                              |
-| Inspect widget hierarchy      | `mcp__plugin_flutter_flutter-ultra-runtime__get_widget_tree`                                          |
-| Run arbitrary Dart in-app     | `mcp__plugin_flutter_flutter-ultra-runtime__evaluate`                                                 |
-| Tap / enter text (marionette) | `mcp__marionette__tap`, `mcp__marionette__enter_text`                                                 |
-| Scroll to element             | `mcp__marionette__scroll_to`                                                                          |
-| Read runtime errors           | `mcp__plugin_flutter_flutter-ultra-runtime__get_runtime_errors`                                       |
-| Read app logs                 | `mcp__plugin_flutter_flutter-ultra-runtime__get_logs`                                                 |
-| Screenshot                    | `mcp__plugin_flutter_flutter-ultra-runtime__screenshot`                                               |
-| Web fill / click              | `mcp__plugin_flutter_flutter-ultra-browser__fill`, `mcp__plugin_flutter_flutter-ultra-browser__click` |
-| Wait for URL (OAuth)          | `mcp__plugin_flutter_flutter-ultra-browser__wait_for_url`                                             |
-| Native permission grant       | `mcp__plugin_flutter_flutter-ultra-native-mobile__native_permission_grant`                            |
+- **Element not found**: call `mcp__plugin_flutter_flutter-ultra-runtime__get_widget_tree` to find where the element is. Wait up to 3s via `mcp__plugin_flutter_flutter-ultra-gesture__wait_for`.
+- **Wrong route**: `mcp__plugin_flutter_flutter-ultra-runtime__evaluate` to read `GoRouter.of(context).routerDelegate.currentConfiguration.fullPath`, then navigate to the correct starting point.
+- **Text field requires focus**: tap the field first with `mcp__plugin_flutter_flutter-ultra-gesture__tap`, then `mcp__plugin_flutter_flutter-ultra-gesture__enter_text`.
+- **Async loading**: `mcp__plugin_flutter_flutter-ultra-runtime__widget_exists` to check for `CircularProgressIndicator`; wait and retry.
+- **Code change mid-flow**: `mcp__plugin_flutter_flutter-ultra-runtime__hot_reload` after edits, then re-verify the widget tree.
 
 ## Example
 
 ```
-User: "Drive the login flow for user@invora.app with password hunter2, then open the first invoice."
-
-1. discover_sessions → attach(sessionId: "flutter-1")
-2. screenshot → step-0-start.png (confirm login screen)
-3. find_widget(key: "email-field") → found
-4. evaluate: set email controller value to "user@invora.app"
-5. find_widget(key: "password-field") → found
-6. evaluate: set password controller value to "hunter2"
-7. find_widget(key: "sign-in-button") → found; marionette tap(key: "sign-in-button")
-8. evaluate: await SchedulerBinding.instance.endOfFrame (wait for navigation)
-9. find_widget(key: "dashboard-root") → found (login succeeded)
-10. screenshot → step-1-dashboard.png
-11. evaluate: context.go('/invoices')
-12. find_widget(text: "Invoice #1") → found; marionette tap(text: "Invoice #1")
-13. find_widget(key: "invoice-detail-root") → found
-14. screenshot → step-2-invoice-detail.png
-
-Summary: 3 major steps completed, all passed. Final route: /invoices/1.
+User: "Drive the login flow for user@example.com, then open the first invoice."
+
+1. discover_sessions -> attach(sessionId: "flutter-1")
+2. screenshot -> confirm login screen visible
+3. interactive_elements -> found: email-field, password-field, sign-in-button
+4. tap(key: "email-field") -> enter_text(text: "user@example.com")
+5. tap(key: "password-field") -> enter_text(text: "password123")
+6. tap(key: "sign-in-button")
+7. wait_for(key: "dashboard-root") -> found
+8. screenshot -> dashboard loaded
+9. evaluate: context.go('/invoices')
+10. wait_for(text: "Invoice #1") -> found
+11. tap(text: "Invoice #1")
+12. wait_for(key: "invoice-detail") -> found
+13. screenshot -> invoice detail visible
+-> "3 major steps completed. Final route: /invoices/1"
 ```
 
 ## See also
 
-- Sibling skill: `flutter-tour` for passive route screenshot sweeps (no interaction)
-- Sibling skill: `flutter-test` for orchestrated patrol E2E test runs
-- `mcp__marionette__*` — native gesture and text tools via VM service extensions
+- `flutter-tour` — passive route screenshot sweeps without interaction
+- `flutter-test` — orchestrated patrol E2E test runs
+- `flutter-debug` — triage runtime errors encountered during a flow