maui-devflow-debug
/maui-devflow-debug
Run build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated to MAUI. INVOKES: maui devflow CLI, dotnet CLI, Android adb/android tools, and Apple simctl tools.
- Author
- yurkinh ↗
- Repository
- plugin.maui.calendar ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 9
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated to MAUI. INVOKES: maui devflow CLI, dotnet CLI, Android adb/android tools, and Apple simctl tools.
Original author description
Run build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated to MAUI. INVOKES: maui devflow CLI, dotnet CLI, Android adb/android tools, and Apple simctl tools.
How it works
- When to Use
- Route Elsewhere
- Core Loop
- Critical Anti-patterns
- Stop Signals
- Reference Map
SKILL.md preview
--- name: maui-devflow-debug description: >- Run build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated to MAUI. INVOKES: maui devflow CLI, dotnet CLI, Android adb/android tools, and Apple simctl tools. --- # DevFlow Debug Use this skill for the active debugging loop after a MAUI app has DevFlow packages and `builder.AddMauiDevFlowAgent()` registered. ## When to Use - Build and run a MAUI app on Android, iOS, Mac Catalyst, macOS, Windows, or GTK. - Choose or create a simulator/emulator for a project. - Wait for a DevFlow agent, inspect the visual tree, tap/fill UI, or capture screenshots. - Recover from DevFlow connection failures after the app is integrated, including broker, port, and Android adb forwarding issues. - Debug Blazor Hybrid content through DevFlow WebView/CDP commands. - Read app logs, network captures, preferences, device info, or recordings through DevFlow. - Iterate on an app bug with a build -> deploy -> inspect -> fix loop. ## Route Elsewhere - If DevFlow packages or `MauiProgram.cs` registration are missing, use `maui-devflow-onboard`. - If the failure is a generic build or SDK issue with no DevFlow angle, use normal .NET/MAUI diagnostics. ## Core Loop 1. Confirm the app is already integrated: ```bash grep -rl "Microsoft.Maui.DevFlow" --include="*.csproj" . ``` If no project has DevFlow package references, stop and switch to `maui-devflow-onboard`. 2. Pick the target framework and launch target. Do not assume `net10.0`; inspect the project first. ```bash grep -i "TargetFramework" *.csproj Directory.Build.props 2>/dev/null ``` 3. Start or select the device/emulator. For Android and iOS, avoid reusing a simulator/emulator that is already running another app under investigation. 4. Launch the app and keep the launch process alive when required. - iOS, Android, and Mac Catalyst `dotnet build -t:Run` usually block for the app lifetime. - GTK `dotnet run` blocks for the app lifetime. - macOS AppKit builds can exit after compiling; launch the `.app` separately. 5. Wait for the DevFlow agent before inspecting UI: ```bash maui devflow wait maui devflow ui tree --depth 3 --fields "id,type,text,automationId" ``` If `wait`, `list`, or `ui tree` cannot connect after the app is running, load `references/connectivity.md` and recover the broker/agent connection before continuing. 6. Inspect, interact, capture evidence, then edit the app and repeat from launch. ## Critical Anti-patterns - Do not treat an empty `maui devflow list` as proof the project is not integrated. `list` is runtime state; project files are source of truth. - Do not use arbitrary sleeps after launch. Use `maui devflow wait` to gate on the actual agent connection. - Do not kill an async `dotnet build -t:Run` or `dotnet run` shell while you still need the app; that often kills the app. - Do not reuse a busy simulator/emulator when multiple MAUI apps or agents may be running. - Do not debug Blazor WebView DOM issues through the native visual tree alone; use the WebView/CDP commands. ## Stop Signals - Stop and switch to `maui-devflow-onboard` when package references or `AddMauiDevFlowAgent()` are absent. - Stop and ask which project, device, or agent to target when multiple candidates match. - Stop rebuilding after two identical failures until you inspect the first meaningful build/runtime error. - Stop using screenshots for exact property values; query the visual tree or properties instead. ## Reference Map Load these only when needed: - `references/setup.md` - detailed integration, package, entitlement, and update notes. - `references/connectivity.md` - broker, agent, port, Android forwarding, and "no agents connected" recovery. - `references/android.md` - Android SDK, emulator, adb, build, deploy, and port forwarding details. - `references/ios-and-mac.md` - iOS simulator, Mac Catalyst, permissions, entitlements, and Apple tooling. - `references/macos.md` - macOS AppKit project shape, launch model, and troubleshooting. - `references/linux.md` - GTK/Linux launch, packages, and WebKitGTK notes. - `references/batch.md` - batching multiple DevFlow UI/WebView operations. - `references/troubleshooting.md` - build, connection, CDP, and platform-specific failure recovery.
Files in this package (9)
- SKILL.md 5 KB
- references/android.md 8 KB
- references/batch.md 2 KB
- references/connectivity.md 4 KB
- references/ios-and-mac.md 12 KB
- references/linux.md 6 KB
- references/macos.md 7 KB
- references/setup.md 13 KB
- references/troubleshooting.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · yurkinh/plugin.maui.calendar | 100 | MIT |
| shinyorg/health | 100 | MIT |
Database snapshot: 13.11.2026 · package version 0ba06a8b4c83 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100maui-devflow-onboard
Add MAUI DevFlow to a .NET MAUI project with agent package references, MauiProgram.cs registration, Blazor WebView support, GTK variants, Central Package Management guidance, and verification commands. USE FOR: first-time DevFlow setup, reviewing what files to edit, choosing… - 100maui-devflow-onboard
Add DevFlow to a MAUI app. USE FOR: package refs, `MauiProgram` registration, Blazor WebView/GTK variants, verification after `maui devflow init`. DO NOT USE FOR: troubleshooting, debugging, UI inspection, or build failures. INVOKES: `maui devflow`, `dotnet`. - 100maui-devflow-onboard
Add DevFlow to a MAUI app. USE FOR: package refs, `MauiProgram` registration, Blazor WebView/GTK variants, verification after `maui devflow init`. DO NOT USE FOR: troubleshooting, debugging, UI inspection, or build failures. INVOKES: `maui devflow`, `dotnet`. - 90maui-devflow-session-review
Review past MAUI DevFlow sessions. USE FOR: DevFlow friction reports, classifying `maui_tap`/`maui_hittest`/`maui_screenshot`/`maui_cdp_webviews` issues vs app bugs, markdown Environment/Findings reports, scrubbed dotnet/maui-labs issue drafts, workaround summaries. Does not run… - 100skiaui-devflow
Adds SkiaUi support to .NET MAUI DevFlow in an app that uses SkiaUi (SkiaUi.Maui, SkUi* controls), so DevFlow and AI agents can find, tap and hit-test drawn controls, which have no platform views and are invisible or untappable through DevFlow's own tree. Copies the dev.skiaui… - 100devflow
Use when working in a DevFlow project with .devflow/ directory and gate-based step-by-step workflows