How do I install the Designing Avalonia Customcontrol Architecture skill?

Run npx skillmds add majiayu000/designing-avalonia-customcontrol-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Designing Avalonia Customcontrol Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Designing Avalonia Customcontrol Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Designing Avalonia Customcontrol Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Designing Avalonia Customcontrol Architecture?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Designing Avalonia Customcontrol Architecture by majiayu000

Name: Designing Avalonia Customcontrol Architecture
Rating: 4.2 (5 reviews)
Author: majiayu000

Designing Avalonia Customcontrol Architecture

Defines the basic solution structure for AvaloniaUI Desktop Applications using CustomControl. Use when creating new AvaloniaUI projects or designing stand-alone control styles with ControlTheme.

majiayu000 c47e759 2 files · 3.7 KB Updated Sep 9, 2026 567 repo stars

File contents

6.5 Writing AXAML Code

When generating AXAML code, use CustomControl with ControlTheme for Stand-Alone Control Style
Purpose: Theme separation and minimizing style dependencies

6.5.1 AvaloniaUI Custom Control Library Project Structure

Recommended Project Structure:

YourAvaloniaSolution
├── YourCustomControlProject1/
│    ├── Properties/
│    │   ├── AssemblyInfo.cs            ← AssemblyInfo.cs definition
│    ├── Themes/
│    │   ├── Generic.axaml            ← ControlTheme definition
│    │   ├── CustomButton1.axaml       ← Individual control theme
│    │   └── CustomTextBox1.axaml      ← Individual control theme
│    ├── CustomButton1.cs
│    └── CustomTextBox1.cs
└── YourCustomControlProject2/
    ├── Properties/
    │   ├── AssemblyInfo.cs            ← AssemblyInfo.cs definition
    ├── Themes/
    │   ├── Generic.axaml            ← ControlTheme definition
    │   ├── CustomButton2.axaml       ← Individual control theme
    │   └── CustomTextBox2.axaml      ← Individual control theme
    ├── CustomButton2.cs
    └── CustomTextBox2.cs

6.6 ⚠️ Distinguishing ResourceInclude vs MergeResourceInclude

ResourceInclude: Used in regular ResourceDictionary files (Generic.axaml, Styles, etc.)
MergeResourceInclude: Used only in Application.Resources (App.axaml)

Advantages:

Complete separation of theme and logic based on ControlTheme
Flexible style variations through CSS Classes
State management via Pseudo Classes (:pointerover, :pressed, etc.)
Theme modularization through ResourceInclude
Work can be split by file for team collaboration

6.5.2 Key Differences Between WPF and AvaloniaUI

Item	WPF	AvaloniaUI
File Extension	.xaml	.axaml
Style Definition	Style + ControlTemplate	ControlTheme
State Management	Trigger, DataTrigger	Pseudo Classes, Style Selector
CSS Support	❌	✅ (Classes attribute)
Resource Merging	MergedDictionaries + ResourceDictionary	MergedDictionaries + ResourceInclude
Dependency Props	DependencyProperty	StyledProperty, DirectProperty

---name: designing-avalonia-customcontrol-architecturedescription: Defines the basic solution structure for AvaloniaUI Desktop Applications using CustomControl. Use when creating new AvaloniaUI projects or designing stand-alone control styles with ControlTheme.--- # 6.5 Writing AXAML Code - **When generating AXAML code, use CustomControl with ControlTheme for Stand-Alone Control Style** - Purpose: Theme separation and minimizing style dependencies #### 6.5.1 AvaloniaUI Custom Control Library Project Structure **Recommended Project Structure:** ``` YourAvaloniaSolution ├── YourCustomControlProject1/ │ ├── Properties/ │ │ ├── AssemblyInfo.cs ← AssemblyInfo.cs definition │ ├── Themes/ │ │ ├── Generic.axaml ← ControlTheme definition │ │ ├── CustomButton1.axaml ← Individual control theme │ │ └── CustomTextBox1.axaml ← Individual control theme │ ├── CustomButton1.cs │ └── CustomTextBox1.cs └── YourCustomControlProject2/ ├── Properties/ │ ├── AssemblyInfo.cs ← AssemblyInfo.cs definition ├── Themes/ │ ├── Generic.axaml ← ControlTheme definition │ ├── CustomButton2.axaml ← Individual control theme │ └── CustomTextBox2.axaml ← Individual control theme ├── CustomButton2.cs └── CustomTextBox2.cs ``` # 6.6 ⚠️ Distinguishing ResourceInclude vs MergeResourceInclude - **ResourceInclude**: Used in regular ResourceDictionary files (Generic.axaml, Styles, etc.) - **MergeResourceInclude**: Used only in Application.Resources (App.axaml) **Advantages:** - Complete separation of theme and logic based on ControlTheme - Flexible style variations through CSS Classes - State management via Pseudo Classes (:pointerover, :pressed, etc.) - Theme modularization through ResourceInclude - Work can be split by file for team collaboration #### 6.5.2 Key Differences Between WPF and AvaloniaUI | Item | WPF | AvaloniaUI | | ----------------- | --------------------------------------- | ------------------------------------ | | File Extension | .xaml | .axaml | | Style Definition | Style + ControlTemplate | ControlTheme | | State Management | Trigger, DataTrigger | Pseudo Classes, Style Selector | | CSS Support | ❌ | ✅ (Classes attribute) | | Resource Merging | MergedDictionaries + ResourceDictionary | MergedDictionaries + ResourceInclude | | Dependency Props | DependencyProperty | StyledProperty, DirectProperty |

Frequently asked questions