skills.rest
peterblazejewicz
peterblazejewiczCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Review Avalonia project structure and extract design tokens with version-specific guidance.

7|Updated Jan 11, 2026
Search Tags:#theming#code review#migration#design tokens#dotnet#avalonia#xaml
One-click install
npx skills add https://github.com/peterblazejewicz/claude-plugins --skill review-peterblazejewicz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/peterblazejewicz/claude-plugins/tree/main/plugins/avalonia-dev/skills/review
Command: npx skills add https://github.com/peterblazejewicz/claude-plugins --skill review-peterblazejewicz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Avalonia and MAUI projects often accumulate hardcoded colors, fonts, and spacing scattered across AXAML files, making theming inconsistent and maintenance painful. This Skill performs a structured architecture review that identifies these issues and produces a phased migration plan toward a token-based design system. ## Core Features & Use Cases - Design Token Extraction: Detects hardcoded colors, font sizes, and spacing in AXAML files and organizes them into centralized token files (Colors, Typography, Spacing, Elevation). - Version-Specific Review: Detects whether the project targets Avalonia 11.x or 12.x and applies appropriate checks, such as compiled bindings (x:DataType), accessibility properties, and page-based navigation for v12. - Migration Planning: Produces a four-phase migration plan (token extraction, style consolidation, control isolation, project splitting) with risk levels and rollback strategies. - Use Case: A team inheriting a legacy Avalonia 11 app with hardcoded hex colors in every view can run this review to get an assessment, a target folder structure, and step-by-step guidance to adopt a light/dark theme system and plan the upgrade to Avalonia 12. ## Quick Start Ask the assistant to review your Avalonia project structure and suggest design token and theming improvements.

Frequently Asked Questions about review

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

FAQPage Schema
How do I extract design tokens from an Avalonia project?▼

Search AXAML files for hardcoded hex colors, font sizes, and padding values, then move them into centralized ResourceDictionary files like Colors.axaml, Typography.axaml, and Spacing.axaml. Reference them in views with StaticResource or DynamicResource instead of literal values.

How to review Avalonia project structure and theming?▼

Start by detecting the Avalonia version from package references, then audit where styles and colors are defined, flag hardcoded values and duplicate styles, and propose a target folder layout. Finish with a phased migration plan ordered by risk and impact.

Does this support Avalonia 12 compiled bindings?▼

Yes. For Avalonia 12 projects it checks that views and controls declare x:DataType so compiled bindings work with type safety, and flags Binding usage without it. Avalonia 12 enables compiled bindings by default.

When should I use DynamicResource vs StaticResource in Avalonia?▼

Use DynamicResource for theme-aware values like colors that change between light and dark themes, since StaticResource will not update on theme switches. Use StaticResource for fixed values such as spacing, corner radius, and font sizes.

What is the migration path from Avalonia 11 to Avalonia 12?▼

Key changes include renaming SystemDecorations to WindowDecorations, adding x:DataType for compiled bindings, targeting net10.0, and replacing removed APIs like PropertyPath. Most teams complete the migration within a sprint with minor code changes.

When should an Avalonia app be split into multiple projects?▼

Split into separate class libraries when the app has 30+ views or 15+ custom controls, when multiple applications share the theme, or when independent versioning is needed. Smaller projects should just reorganize folders within the existing project.

Related Skills

Explore More Software Engineering Skills→
ShareXShareX
309

design-ui-window

Redesign Avalonia .axaml views with standardized layout, typography, and styling.

Official
Advanced
DergaczDergacz

10x-tdd

Automate TDD implementation by executing test-first steps per technical plan phase.

Community
Advanced
davepoondavepoon
3.4k

check

Run CIAgent regression checks and interpret results after changing an AI agent's code, prompts, or knowledge base.

Community
Intermediate
AbsolutelySkilledAbsolutelySkilled
207

design-systems

Standardize design tokens, theming, and Storybook documentation for UI libraries.

Official
Advanced