القائمة
Use when migrating WPF source projects, classic .NET Framework WPF projects, XAML, dependency properties, commands, resources, or interop to WinUI 3 or Uno.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | wpf-to-winui-migration |
| description | Use when migrating WPF source projects, classic .NET Framework WPF projects, XAML, dependency properties, commands, resources, or interop to WinUI 3 or Uno. |
Use this skill for WPF source migrations, including SDK-style WPF projects, old-style .NET Framework WPF projects, and mixed evidence that must not be silently treated as Avalonia.
dotnet run --project src/MigrateToWinUI.Cli -- analyze <sln|csproj|dir> --source wpf --target both --format json --report out/migration/wpf-analysis.json
dotnet run --project src/MigrateToWinUI.Cli -- plan <input> --source wpf --target both --format md --out out/migration/wpf-plan.md
dotnet run --project src/MigrateToWinUI.Cli -- detail <input> --source wpf --target both --format md --out out/migration/wpf-dashboard.md
dotnet run --project src/MigrateToWinUI.Cli -- convert <input> --source wpf --target winui3 --dry-run --preview out/migration/wpf-preview.txt
dotnet run --project src/MigrateToWinUI.Cli -- compose <input> --source wpf --target both --out out/target-projects --project-name MigratedWpfApp --clean --allow-manual-review
WP2U030x: dependency properties, routed events, commands, validation/coercion metadata.WP2U040x: triggers, templates, resources, visual states.WP2U060x: platform services, windowing, dialogs, clipboard, file access.WP2U070x: drawing, media, interop, HwndHost, printing/documents.MTW0001: mixed Avalonia/WPF evidence. Ask for explicit --source.Window/Page shell decisions product-specific..NET Framework project diagnostics as migration inventory, not failures by themselves.