What problem does it solve? Developers moving from WPF to AvaloniaUI often struggle with how to structure custom control libraries and where to define styles, since AvaloniaUI replaces Style/ControlTemplate with ControlTheme and uses different resource merging rules. This Skill provides a concrete project layout and AXAML authoring rules so new AvaloniaUI desktop projects start with a clean, theme-separated architecture. ## Core Features & Use Cases - Custom Control Library Structure: Defines a recommended solution layout with Themes/Generic.axaml, per-control AXAML theme files, AssemblyInfo.cs XmlnsDefinition, and StyledProperty-based control classes. - ResourceInclude vs MergeResourceInclude Guidance: Clarifies that ResourceInclude belongs in regular ResourceDictionaries like Generic.axaml while MergeResourceInclude is only for App.axaml Application.Resources. - WPF-to-AvaloniaUI Migration Reference: Provides a comparison table covering file extensions, ControlTheme vs ControlTemplate, Pseudo Classes vs Triggers, CSS Classes support, and StyledProperty vs DependencyProperty. - Use Case: When scaffolding a new AvaloniaUI desktop app with reusable custom buttons and text boxes, use this Skill to generate the control library project, theme files, and sample App/MainWindow code following the ControlTheme pattern. ## Quick Start Create a new AvaloniaUI custom control library project with a CustomButton using ControlTheme and StyledProperty following the recommended structure.