Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
58
41%
Does it follow best practices?
Impact
86%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-avalonia-layout-zafiro/SKILL.mdTheme file organization and DynamicResource
Colors file exists
100%
100%
DynamicResource for brushes
91%
91%
No hardcoded color literals in views
80%
100%
Grouped style files
100%
100%
Theme.axaml aggregator
87%
100%
MergedDictionaries usage
100%
100%
Icons.axaml resource file
0%
0%
Icons in MergedDictionaries
0%
0%
Classes over inline properties
100%
100%
No repeated inline properties
100%
100%
Semantic containers and icon usage
HeaderedContainer used
100%
100%
No Border-as-header
100%
100%
EdgePanel for aligned rows
100%
100%
Card container used
0%
0%
Icon markup extension
0%
100%
IconOptions for icon styling
0%
100%
No deeply nested Grid/StackPanel
100%
100%
Classes for styling variants
100%
100%
DynamicResource for colors
62%
100%
EdgePanel over Grid for label-value
100%
100%
Behaviors over converters and shared styles
Interaction.Behaviors used
0%
58%
No code-behind event handlers
100%
100%
No IValueConverter for simple logic
100%
100%
ViewModel exposes display-ready properties
100%
100%
Classes-based styling
100%
100%
No inline repeated properties
30%
80%
DynamicResource for colors
0%
25%
Generic component or EdgePanel for row pattern
30%
100%
No deep nesting
87%
62%
Converter only for purely visual reusable case
100%
100%
f1697b6
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.