wieslawsoltes

Umbrella skill for building, reviewing, designing, porting, and migrating Avalonia applications with modern XAML/C# patterns on Avalonia 11.3.12. Use when the request is broad Avalonia work or when another specialist skill has not yet been selected; route quickly to focused skills for startup, bindings, styling, controls, layout, rendering, testing, design systems, or HTML/WinForms/WPF/WinUI/Avalonia 12 migration work.

Repo-local umbrella skill for building, reviewing, designing, porting, and migrating Avalonia applications with modern XAML/C# patterns on Avalonia 11.3.12. Use when working inside this repository and the request is broad Avalonia work; route quickly to the focused plugin skills for startup, bindings, styling, controls, layout, rendering, testing, design systems, or HTML/WinForms/WPF/WinUI/Avalonia 12 migration work.

Plan and execute migration from Avalonia 11.3.12 to Avalonia 12 using the repository's dedicated migration lane. Use for breaking-change review, source-backed API delta lookup, migration sequencing, and upgrades that should stay grounded in the current published Avalonia 12 documentation and generated artifacts.

Design or review Avalonia validation, data-error presentation, accessibility semantics, automation properties, focus order, and testable UI metadata. Use for validation pipelines, screen-reader support, keyboard-only UX, automation-tree issues, or accessibility hardening.

Implement or troubleshoot Avalonia compiled bindings, runtime XAML loading, converters, markup extensions, binding notifications, dynamic resources, and AOT-safe XAML patterns. Use for `x:DataType`, `CompiledBinding`, converter wiring, `AvaloniaRuntimeXamlLoader`, resource lookup issues, or runtime markup refactors.

Design or troubleshoot Avalonia startup wiring, `AppBuilder` configuration, application lifetimes, platform bootstrap, XAML compiler setup, and AOT-friendly build configuration. Use for desktop or single-view startup, `App.axaml` / `App.xaml.cs` composition, platform entrypoints, trimming or NativeAOT readiness, or startup refactors.

Build or troubleshoot Avalonia controls, control themes, windows, popups, menus, tray integration, native menus, top-level services, and notification surfaces. Use for templated control authoring, popup behavior, custom chrome, dialog flows, menu systems, or per-control API guidance.

Design polished Avalonia design systems with reusable tokens, typography, spacing, shell composition, dense workflow UX, motion, and governance rules. Use for professional UI direction, design-token architecture, responsive layout systems, information architecture, or high-quality desktop workflow design.

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.

Install, inspect, automate, record, replay, and verify Avalonia applications through Chrome DevTools Protocol (CDP), including dual-CDP orchestration of CdpInspectorApp and CdpSampleApp.

Comprehensive guide for choosing, installing, wiring, and troubleshooting XamlToCSharpGenerator (AXSG) packages in Avalonia projects. Use when Codex needs to add AXSG to an Avalonia app, select among the public AXSG packages or tooling artifacts, configure SourceGen MSBuild switches, set up runtime or hot reload support, embed AXSG editor/language-service tooling, or compose lower-level compiler/runtime packages in this repository.

Implement, troubleshoot, and review TreeDataGrid usage in this repository by grounding work in Lunet articles (`site/articles/**`) and generated API data (`src/Avalonia.Controls.TreeDataGrid/obj/Release/*/Avalonia.Controls.TreeDataGrid.api.json`). Use when tasks involve TreeDataGrid setup, flat or hierarchical sources, columns/cells/rows, selection, editing, drag and drop, XAML themes/templates, performance/primitives internals, or public API lookup.

Configure and troubleshoot Lunet static sites using docs-first workflows focused on `config.scriban`, content front matter, `menu.yml`, layouts/includes, full plugin configuration, GitHub Actions deployment, and build/serve behavior. Use for Lunet site setup and maintenance; handle `api.dotnet` only when the user explicitly asks for API documentation features.

Use Inspector CLI for Avalonia inspection, debugging, live preview introspection, editing/mutation workflows, and troubleshooting across stub, host, and process modes.

Build, review, design, migrate, and optimize Uno Platform applications and Uno framework source-tree changes with modern WinUI 3 XAML/C# patterns, Uno.Sdk configuration, typed bindings, dependency properties, control templating, Skia or native rendering choices, design systems, and platform-specific C#/XAML. Use for tasks involving Uno app startup and solution structure, target-platform setup, view and viewmodel composition, x:Bind or binding work, themes and resources, custom controls, Hot Reload or Dev Server workflows, performance, troubleshooting, testing, work inside the `/Users/wieslawsoltes/GitHub/uno` repo, or Avalonia-to-Uno migration work.