avalonia-bindings-and-xaml

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.

Stars 57

Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/wieslawsoltes/development-plugin-for-avalonia/tree/main/skills/avalonia-bindings-and-xaml

SKILL.md

Avalonia Bindings and XAML

Start with:

../../references/02-bindings-xaml-aot.md
../../references/41-xaml-compiler-and-build-pipeline.md
../../references/45-value-converters-single-multi-and-binding-wiring.md
../../references/46-binding-value-notification-and-instanced-binding-semantics.md

Load these as needed:

../../references/42-runtime-xaml-loader-and-dynamic-loading.md
../../references/44-runtime-xaml-manipulation-and-service-provider-patterns.md
../../references/49-adaptive-markup-and-dynamic-resource-patterns.md
../../references/50-relative-static-resource-and-name-resolution-markup.md
../../references/43-xaml-in-libraries-and-resource-packaging.md

Workflow

Default to compiled bindings with x:DataType.
Keep template, converter, and markup-extension wiring typed where possible.
Use runtime XAML loading only when dynamic loading is a real requirement.
Verify resource lookup, namescope, and relative binding assumptions explicitly.

Rules

Prefer generated or compiled binding paths over runtime parser fallbacks.
Treat RequiresUnreferencedCode and runtime XAML APIs as explicit tradeoffs.
Keep converters small and deterministic; prefer typed state or projection when possible.
Use the generated API index only for signature lookup, not as the main workflow guide.