菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | api-surface-lifecycle |
| description | 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 this skill when scanning framework assemblies, matching source APIs to WinUI or Uno, producing coverage reports, creating rule-gap catalogs, or repeating pinned rescans.
README.mdspecs/001-migration-core/contracts/cli.mdspecs/001-migration-core/contracts/api-surface.md, specs/001-migration-core/contracts/api-surface.schema.jsonspecs/001-migration-core/api-surface/README.mdspecs/001-migration-core/rule-family-catalog.mdspecs/001-migration-core/remaining-work.mdscripts/api-surface/Before scanning, pin all inputs:
avalonia, wpf, winui, or uno.--package-id and --package-version.builtins, a rule-pack file, or a rule-pack directory.The scanner sorts assembly paths and writes stable catalog data. Do not mix floating package versions or machine-specific discovered assemblies into committed artifacts.
Scan source or target assemblies:
dotnet run --project src/MigrateToWinUI.Cli -- api scan --framework avalonia --assembly "$HOME/.nuget/packages/avalonia/11.3.7/lib/netstandard2.0/Avalonia.Base.dll" --package-id Avalonia --package-version 11.3.7 --out out/api/avalonia.json --format json
dotnet run --project src/MigrateToWinUI.Cli -- api scan --framework wpf --assembly "/absolute/path/PresentationFramework.dll" "/absolute/path/PresentationCore.dll" "/absolute/path/WindowsBase.dll" "/absolute/path/System.Xaml.dll" --package-id Microsoft.WindowsDesktop.App.Ref --package-version 10.0.5 --out out/api/wpf.json --format json
dotnet run --project src/MigrateToWinUI.Cli -- api scan --framework winui --assembly "/absolute/path/Microsoft.UI.Xaml.dll" --package-id Microsoft.WindowsAppSDK --package-version "<pinned-version>" --out out/api/winui.json --format json
dotnet run --project src/MigrateToWinUI.Cli -- api scan --framework uno --assembly "/absolute/path/Uno.UI.dll" --package-id Uno.UI --package-version "<pinned-version>" --out out/api/uno.json --format json
For committed WPF reference lanes, use the repo helpers instead of hand-maintaining assembly paths:
scripts/api-surface/scan-pinned-wpf-reference-assemblies.sh
scripts/api-surface/classify-pinned-wpf-reference-assemblies.sh
Match each source catalog to a target catalog:
dotnet run --project src/MigrateToWinUI.Cli -- api match --source out/api/avalonia.json --target out/api/winui.json --out out/api/avalonia-to-winui.matches.json --format json
dotnet run --project src/MigrateToWinUI.Cli -- api match --source out/api/wpf.json --target out/api/uno.json --out out/api/wpf-to-uno.matches.json --format json
Exit code 2 means unmatched APIs remain. Continue to coverage/gap reporting instead of treating that as a shell failure when the task is classification planning.
Run coverage with built-in rules first, then with any explicit rule packs under review:
dotnet run --project src/MigrateToWinUI.Cli -- api coverage --matches out/api/avalonia-to-winui.matches.json --rules builtins --out out/api/avalonia-to-winui.coverage.json --format json
dotnet run --project src/MigrateToWinUI.Cli -- api coverage --matches out/api/wpf-to-uno.matches.json --rules builtins --out out/api/wpf-to-uno.coverage.md --format md
Coverage acceptance is about classification, not automation:
classificationCoveragePercent must be 100.0 for accepted source catalogs.unclassifiedSymbolIds and conflictingMatchIds must be empty.automationCoveragePercent can be lower and must not be used as a classification release gate.Exit code 3 means unclassified APIs remain.
Generate an API rule-gap catalog whenever coverage is incomplete or new API rows need authoring:
dotnet run --project src/MigrateToWinUI.Cli -- api gaps --source out/api/avalonia.json --matches out/api/avalonia-to-winui.matches.json --rules builtins --out out/api/avalonia-to-winui.gaps.json --format json
dotnet run --project src/MigrateToWinUI.Cli -- api gaps --source out/api/wpf.json --matches out/api/wpf-to-uno.matches.json --rules builtins --out out/api/wpf-to-uno.gaps.md --format md
Use the gap catalog to drive rule-family work. Each row should have one effective classification or a suggested family for authoring.
Use manifest-driven rescans for pinned catalog refreshes:
dotnet run --project src/MigrateToWinUI.Cli -- api rescan --manifest specs/001-migration-core/api-surface/manifests/wpf-pinned-reference-assemblies.json --out specs/001-migration-core/api-surface
For ad hoc rescan manifests, require each scan entry to pin framework, assemblies, package id, package version, target framework when relevant, output path, and optional baseline/diff path.
Output checks:
.diff.json artifact is written per scan entry.Pause before accepting or committing API artifacts when:
100.0 classification coverage.Prefer structured CLI output, then use text search for triage:
rg -n '"classificationCoveragePercent"|"automationCoveragePercent"|"unclassifiedApiCount"|"unresolvedApiCount"|"classification": "Unknown"' out/api specs/001-migration-core/api-surface
rg -n 'AW2U|WP2U|ManualReview|Unsupported|OutOfScope|SafeRewrite|DiagnosticOnly' out/api specs/001-migration-core/api-surface
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 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.