Turn official .NET/MAUI release notes into an app upgrade plan. USE FOR: breaking-change summaries, Xcode/JDK/Android SDK requirements, global.json/workload/package updates, CI image changes, migration checklists, validation plans, live version lookup. DO NOT USE FOR: authoring workload release notes or marketing copy.
Plan Xamarin.Forms to MAUI migrations. USE FOR: audits, fresh dotnet new maui, namespace updates, DependencyService to DI, MessagingCenter replacement, renderer triage, MauiProgram, permissions, parity planning. DO NOT USE FOR: brand-new MAUI apps, native SDK bindings, backend.
Create Android slim bindings for MAUI/.NET Android. USE FOR: Native Library Interop, thin Kotlin/Java wrapper design, building wrapper AARs with Gradle, Java-friendly callbacks, @JvmStatic, and dependencies of slim wrappers. DO NOT USE FOR: direct/full Java/Kotlin bindings or generated-code/Metadata.xml repairs (use…
Automate MAUI app state through DevFlow Actions. USE FOR: [DevFlowAction] shortcuts, login, seed data, deep screens. DO NOT USE FOR: arbitrary methods, DI internals, UI MCP tools, connectivity, or build/deploy issues.
Diagnose DevFlow agent connectivity. USE FOR: maui devflow connection failures, agent not found, ports, adb forwarding, broker. DO NOT USE FOR: build failures, setup, visual tree, or Blazor CDP.
Discover MAUI workload metadata from live NuGet APIs. USE FOR: workload manifest lookup, WorkloadDependencies.json, v3-flatcontainer, CLI-to-NuGet version conversion, Xcode/JDK/Android SDK requirements, CI sdkmanager packages, packageid:Microsoft.Maui.Controls. DO NOT USE FOR: installing workloads, build debugging, or…
Review past MAUI DevFlow sessions. USE FOR: DevFlow friction reports, classifying mauitap/mauihittest/mauiscreenshot/mauicdpwebviews issues vs app bugs, markdown Environment/Findings reports, scrubbed dotnet/maui-labs issue drafts, workaround summaries. Does not run live maui devflow. DO NOT USE FOR: fixing bugs…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: