Menu
Use when creating, extending, or reviewing AW2U/WP2U migration rules, rule packs, API gap classifications, or diagnostics.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | rule-authoring-and-gaps |
| description | Use when creating, extending, or reviewing AW2U/WP2U migration rules, rule packs, API gap classifications, or diagnostics. |
Use this skill to add migration rules or classify uncovered APIs.
specs/001-migration-core/rule-family-catalog.mdspecs/001-migration-core/api-surface/classifications/rulepacks/api gapsapi coverage and relevant golden tests.Safe: deterministic text/AST rewrite with strong preconditions and tests.Review: rewrite can be previewed but requires human confirmation.Manual: diagnostic/report only.Never increase automation coverage by hiding unknowns as unsupported without rationale.