maui-devflow-debug
/maui-devflow-debug
Prowadzi pętle budowania, wdrażania, inspekcji i poprawek w aplikacjach .NET MAUI z zintegrowanym DevFlow: uruchamianie, połączenia agenta, drzewo wizualne, zrzuty ekranu, Blazor WebView i logi.
- Autor
- yurkinh ↗
- Repozytorium
- plugin.maui.calendar ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 14.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 9
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 14.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi pętle budowania, wdrażania, inspekcji i poprawek w aplikacjach .NET MAUI z zintegrowanym DevFlow: uruchamianie, połączenia agenta, drzewo wizualne, zrzuty ekranu, Blazor WebView i logi.
Oryginalny opis (EN)
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.
Jak działa
- When to Use
- Route Elsewhere
- Core Loop
- Critical Anti-patterns
- Stop Signals
- Reference Map
Podgląd SKILL.md
--- 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.
Pliki w paczce (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
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · yurkinh/plugin.maui.calendar | 100 | MIT |
| shinyorg/health | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 0ba06a8b4c83 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100maui-devflow-onboard
Dodaje MAUI DevFlow do projektu .NET MAUI: pakiety agenta, rejestracja w MauiProgram.cs, Blazor WebView, warianty GTK, Central Package Management i polecenia weryfikacyjne przy pierwszej konfiguracji. - 100maui-devflow-onboard
Dodaje DevFlow do aplikacji MAUI: odwołania do pakietów, rejestracja w MauiProgram, warianty Blazor WebView i GTK oraz weryfikacja po uruchomieniu maui devflow init. - 100maui-devflow-onboard
Dodaje DevFlow do aplikacji MAUI: odwołania do pakietów, rejestracja w MauiProgram, warianty Blazor WebView i GTK oraz weryfikacja po uruchomieniu maui devflow init. - 90maui-devflow-session-review
Przegląda zapisane sesje MAUI DevFlow, klasyfikuje problemy narzędzi i błędy aplikacji oraz przygotowuje raporty i szkice zgłoszeń. - 100skiaui-devflow
Dodaje obsługę SkiaUi do DevFlow w aplikacji .NET MAUI, by agent mógł znaleźć i dotknąć kontrolki rysowane na płótnie. - 100devflow
Prowadzi pracę w projekcie DevFlow z katalogiem .devflow/ i krokowymi przepływami z bramkami.