xaml-csharp-development-skill-for-avalonia

Build and migrate Avalonia applications with XAML/C# patterns and compiled bindings.

86|11|Updated Feb 15, 2026

Search Tags:#migration #bindings #design-tokens #avalonia #xaml #fluent-theme

Ready to run

npx skills add https://github.com/wieslawsoltes/xaml-csharp-development-skill-for-avalonia --skill xaml-csharp-development-skill-for-avalonia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: xaml-csharp-development-skill-for-avalonia
Source: https://github.com/wieslawsoltes/xaml-csharp-development-skill-for-avalonia/tree/main
Command: npx skills add https://github.com/wieslawsoltes/xaml-csharp-development-skill-for-avalonia --skill xaml-csharp-development-skill-for-avalonia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Replaces guesswork with a structured, version-aware guide for building, reviewing, migrating, and optimizing Avalonia applications using modern XAML/C# patterns, compiled bindings, and Fluent design tokens.

Core Features & Use Cases

Comprehensive coverage of app startup, data binding, styling, resources, and Avalonia 12 migration planning for 11.3.12 baseline.
Practical workflows for design tokens, FluentTheme customization, and performance considerations across desktop, browser, and mobile targets.
Real-world scenarios including app startup wiring, view/viewmodel composition, compiled bindings, and migration planning.

Quick Start

Load the Avalonia app skeleton and apply the pinned 11.3.12 guidance and 12-migration lane to begin building or refactoring.

Frequently Asked Questions about xaml-csharp-development-skill-for-avalonia

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate my Avalonia application to version 12 from 11.3.12?▼

Migrate Avalonia applications using the version-aware migration lane, which guards against drift during upgrades by enforcing pinned 11.3.12 baseline compatibility and applying AOT/trim considerations for the 12 transition.

How do I configure compiled bindings and FluentTheme design tokens in Avalonia?▼

Configure compiled bindings and FluentTheme design tokens by applying structured XAML/C# patterns for view/viewmodel composition, resource management, and styling customization across desktop, browser, and mobile targets.

Does this Avalonia XAML guidance apply to browser and mobile targets?▼

Yes, the Avalonia XAML guidance applies to desktop, browser, and mobile targets, providing performance considerations and startup lifetime wiring workflows tailored for each platform deployment scenario.

What is the best way to structure app startup lifetimes and templates in Avalonia?▼

Structure app startup lifetimes and templates by loading the Avalonia app skeleton and applying pinned 11.3.12 guidance, ensuring correct wiring for application initialization, view/viewmodel composition, and resource loading.

Why do I need version-pinned compatibility references for Avalonia development?▼

Version-pinned compatibility references prevent framework drift during upgrades by enforcing a strict 11.3.12 baseline, ensuring that compiled bindings, styling, and AOT/trim considerations remain stable across migration and refactoring.

Can I use this Skill to refactor existing Avalonia apps for AOT and trim compatibility?▼

Yes, you can refactor existing Avalonia apps by applying the integrated AOT/trim considerations and performance workflows, ensuring your XAML/C# patterns and compiled bindings remain compatible during optimization.