| name | maui-devflow-onboard |
| description | 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`. |
DevFlow Onboard
Use this skill to add MAUI DevFlow to a project after maui devflow init has installed the DevFlow skills.
When to Use
- The project has no
Microsoft.Maui.DevFlow.* package references yet.
- The user asks how to onboard, initialize, install, integrate, or set up DevFlow.
- The agent needs to choose between standard, Blazor, GTK, or GTK + Blazor DevFlow packages.
- The repo uses Central Package Management and package edits need to be split correctly.
maui devflow init has installed skills and the user asks for the next project edits.
Route Elsewhere
- If package references and
AddMauiDevFlowAgent() are already present but the CLI cannot connect, use maui-devflow-debug.
- If an agent is reachable and the user wants to inspect, tap, screenshot, or debug UI, use
maui-devflow-debug.
Optional Session Feedback Nudge
If onboarding required repeated DevFlow attempts, unclear package/version
workarounds, or a long setup session, ask whether the user wants to run
maui-devflow-session-review to summarize friction for MAUI DevFlow product
feedback. Do not run it automatically.
Workflow
-
Optionally run maui devflow skills check and update bundled skills before editing if it reports update-available-from-current-cli.
-
Find MAUI app projects in the workspace. Prefer app projects with UseMaui, platform TFMs such as ///, or GTK MAUI package references.
