MigrateToWinUI

Use when a coding agent needs to plan and run an end-to-end migration task using MigrateToWinUI without losing deterministic reports or source safety.

Use when a coding agent needs to run MigrateToWinUI analyzer/code-fix CLI workflows, iterate safe rewrite preview/apply rounds, verify after each round, collect JSON/Markdown/SARIF reports, or coordinate Avalonia/WPF migration fixes without hand-assembling commands.

Use for MigrateToWinUI rule-gap classification work: assign API gap rows to AW2U/WP2U families, distinguish direct/equivalent/pattern/manual/unsupported/out-of-scope classifications, review promotion gates, and check coverage without conflating classification with safe rewrite automation.

Use when scanning Avalonia, WPF, WinUI, or Uno public APIs, matching source to target APIs, computing coverage, classifying gaps, or rescanning pinned reference assemblies.

Use for MigrateToWinUI API surface scan, match, coverage, gaps, and rescan workflows across Avalonia, WPF, WinUI, and Uno catalogs, including deterministic command templates, pinned assembly inputs, output checks, and classification versus automation coverage gates.

Use when migrating Avalonia source projects, XAML, controls, resources, or code-behind to WinUI 3 or Uno with the local MigrateToWinUI CLI and rule catalog.

Use for MigrateToWinUI source-unavailable managed DLL/EXE migration work: inventory assumptions, decompile staging, analyze/convert reporting, safe rewrite preview checks, provenance review, BAML/resource manual gates, and validation against the binary migration contract.

Use when source is unavailable and a managed WPF, WinUI, Avalonia, DLL, or EXE must be inventoried, decompiled, analyzed, or staged for migration.

Use when running, inspecting, or improving the Uno Platform visual migration dashboard app for MigrateToWinUI.

Use when creating, extending, or reviewing AW2U/WP2U migration rules, rule packs, API gap classifications, or diagnostics.

Use when an agent needs to migrate, analyze, plan, stage, or compose Avalonia source code toward WinUI 3 or Uno using the MigrateToWinUI repository tooling. Triggers on Avalonia .axaml, Avalonia project files, AW2U diagnostics, WinUI/Uno target shell generation, Avalonia safe rewrites, or Avalonia migration reports.

Use when an agent needs to preview, select, apply, stage, compose, or validate MigrateToWinUI rewrite plans for Avalonia or WPF source migrations. Triggers on safe rewrites, rewritePlans, convert --dry-run, apply --rules, verify, compose --validate, report validation, rule-pack validation, and guarding source mutation.

Use when an agent needs to run, extend, test, or explain the MigrateToWinUI visual migration app for Avalonia or WPF source migration to WinUI or Uno. Triggers on visual app workflows, migration dashboard, preview diffs, sessions, report export, target composition UI, validation history, rule browser, and src/MigrateToWinUI.App changes.

Use when an agent needs to migrate, analyze, plan, stage, or compose WPF source code toward WinUI 3 or Uno using MigrateToWinUI. Triggers on WPF .xaml, System.Windows, UseWPF, ApplicationDefinition, WP2U diagnostics, WPF-to-WinUI rule packs, WPF safe rewrites, and WPF migration reports.

Use when validating migration outputs, writing JSON/SARIF/Markdown reports, checking deterministic output, or summarizing migration status.

Use when migrating WPF source projects, classic .NET Framework WPF projects, XAML, dependency properties, commands, resources, or interop to WinUI 3 or Uno.