No,Category,Guideline,Description,Do,Don't,Code Good,Code Bad,Severity,Docs URL,Applies To,Status,Verified At 1,XAML,Use Avalonia XAML namespace,Avalonia has its own XAML namespace not WPF,xmlns= for Avalonia-specific namespace,WPF xmlns or UWP xmlns,"","",High,https://docs.avaloniaui.net/docs/fundamentals/avalonia-xaml,avalonia 12,active,2026-08-13 2,XAML,Use compiled bindings with x:DataType,Enable compile-time binding validation,x:DataType on root or DataTemplate for compiled bindings,Reflection-based bindings in production,""," without x:DataType",High,https://docs.avaloniaui.net/docs/data-binding/compiled-bindings,avalonia 12,active,2026-08-13 3,XAML,Enable compiled bindings globally,Avalonia 12 enables AvaloniaUseCompiledBindingsByDefault by default so every binding requires x:DataType and remains trim-safe for Native AOT,Keep the Avalonia 12 default or set AvaloniaUseCompiledBindingsByDefault explicitly when documenting the project contract,Disable compiled bindings or rely on runtime binding resolution,true,false,High,https://docs.avaloniaui.net/docs/data-binding/compiled-bindings,avalonia 12,active,2026-08-13 4,XAML,Use #name shorthand for element-to-element bindings,Compiled bindings cannot resolve {Binding ElementName=...} - use the #name shorthand which relies on NameScope lookup,#name shorthand referencing x:Name controls in the same NameScope,ElementName binding inside a compiled-binding scope,""," under compiled bindings",Medium,https://docs.avaloniaui.net/docs/data-binding/compiled-bindings,avalonia 12,active,2026-08-13 5,Styling,Use CSS-like selectors,Avalonia uses selectors not implicit styles,Selectors targeting control types classes and pseudoclasses,WPF-style implicit Style with TargetType,"","", for hover effects,Medium,https://docs.avaloniaui.net/docs/styling/pseudoclasses,avalonia 12,active,2026-08-13 7,Styling,Use nesting selectors,Child and descendant combinators for scoped styles,> for direct child and space for descendant,Flat selectors that match too broadly,"","