メニュー
Use when the user asks to "review Avalonia structure", "review XAML project", "improve theming", "add design tokens", "organize styles", or needs Avalonia/MAUI architecture guidance. Supports Avalonia 11.x and 12.x with version-specific checks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | review |
| description | Use when the user asks to "review Avalonia structure", "review XAML project", "improve theming", "add design tokens", "organize styles", or needs Avalonia/MAUI architecture guidance. Supports Avalonia 11.x and 12.x with version-specific checks. |
| version | 1.1.0 |
This skill provides structured guidance for reviewing and improving Avalonia (and MAUI) project architecture. Focus on design token extraction, separation of concerns, and scalable folder organization.
Supports Avalonia 11.x and 12.x — version-specific guidance is applied based on the detected project version.
Extract all hardcoded values (colors, typography, spacing) into centralized token files. This is the foundation for any theming system and provides immediate benefits with minimal risk.
| Layer | Purpose | Dependencies |
|---|---|---|
| Theme/Tokens | Raw design values (colors, spacing, fonts) | None |
| Theme/Styles | Reusable styles using tokens | Tokens |
| Controls | Shared UI components | Theme |
| Pages | Navigation destinations (Avalonia 12+) | Controls, Theme |
| Views | Feature-specific screens | Controls, Theme |
| ViewModels | Presentation logic | Core/Domain |
App (Host)
|
Features/Views/Pages
|
Controls <-> ViewModels
|
Theme (Tokens + Styles)
|
Core (Non-UI shared code)
Controls and Views consume theme tokens via {StaticResource} or {DynamicResource} references—they never define actual color/spacing values.
Before reviewing, determine the project's Avalonia version:
Directory.Packages.props and Directory.Build.props for PackageReference.*Avalonia or <AvaloniaVersion>*.csproj files for PackageReference.*Avalonia.*VersionRecord the detected version — it determines which version-specific checks apply in Step 5.
Use search tools to find:
#[0-9A-Fa-f]{6,8} in *.axaml filesFontSize="[0-9], Margin="[0-9], Padding="[0-9] in *.axaml filesBackground="# in *.axaml filesCommon problems to flag:
x:DataType declarations on views/controls using bindingsRecommend folder/project organization based on project size:
Small Projects (< 10 views, < 5 custom controls):
Reorganize folders within existing project. See references/project-structure.md for details.
Medium/Large Projects (10+ views, 5+ custom controls):
Extract into separate class library projects. See references/project-structure.md for multi-project layouts.
Prioritize phases by risk and impact:
See references/migration-guide.md for detailed phased approach.
Perform these additional checks after the core review:
Compiled Bindings: Avalonia 12 enables compiled bindings by default. Check if views and controls declare x:DataType for type-safe bindings. Flag {Binding} usage without a corresponding x:DataType as a performance and type-safety issue. Search for <UserControl, <Window, and <ContentPage elements and verify they include x:DataType attributes.
Accessibility: Check for accessibility support:
AutomationProperties.Name on interactive controls (buttons, inputs, toggles)FocusManager API where custom focus behavior is neededNavigation Patterns: If the app implements custom navigation, suggest evaluating Avalonia 12's built-in page-based navigation system:
ContentPage for simple page navigationDrawerPage for drawer/sidebar navigationCarouselPage for gesture-based page switchingTabbedPage via TabView for tabbed interfacesPipsPager for visual page indicatorsNew Token Opportunities: Check for styling properties introduced in Avalonia 12:
PlaceholderForeground on TextBox, AutoCompleteBox, CalendarDatePicker, NumericUpDownLetterSpacing on text elements (inherited attached property on TextElement)API Modernization: Flag deprecated or renamed patterns:
SystemDecorations → WindowDecorationsPropertyPath usage (removed in v12)FuncMultiValueConverter parameter change (IEnumerable → IList)After completing the core review (Steps 1-4), present an upgrade recommendation:
Upgrade Recommendation: Avalonia 12 is now available with significant improvements:
- Up to 1,867% rendering performance improvement in complex scenes
- Compiled bindings enabled by default (better performance + type safety)
- Built-in page-based navigation system (ContentPage, DrawerPage, CarouselPage)
- Native Linux accessibility (AT-SPI2) — first .NET framework with this support
- Themeable client-side window decorations
- New threading model with Dispatcher.CurrentDispatcher and AvaloniaObject.Dispatcher
- Hundreds of bug fixes across all platforms
The migration is designed to be completed within a sprint. Most teams report only minor code changes needed.
If the user indicates they are not ready to upgrade ("not at this time", "not now", "we'll do that later"), acknowledge their decision and do not repeat the recommendation in this session. Continue providing v11-appropriate guidance.
When completing a review, provide these deliverables:
| Deliverable | Description |
|---|---|
| Avalonia Version | Detected version and version-specific notes |
| Assessment Summary | Current state analysis and identified issues |
| Target Structure | Recommended folder/project layout diagram |
| Migration Phases | Ordered steps with priorities and risk levels |
| File Templates | Starter AXAML files for tokens |
| App.axaml Updates | Integration instructions for new theme system |
| Upgrade Path (v11 only) | Key benefits and migration guidance for Avalonia 12 |
Recommend organizing tokens into these files:
| File | Contents |
|---|---|
Colors.axaml | Brand colors, semantic colors, neutral palette, theme variants |
Typography.axaml | Font families, sizes, weights, line heights, letter spacing (v12+) |
Spacing.axaml | Spacing scale, padding presets, margins, corner radius, borders |
Elevation.axaml | Box shadows, z-index values (if applicable) |
See references/design-tokens.md for complete token organization patterns.
ColorSuccess over Green500 where appropriate{DynamicResource}; fixed values (spacing, radius) use {StaticResource}x:DataType to views and controls for type-safe, performant bindingsAutomationProperties.Name and keyboard/focus supportThe initial review focuses on structure and strategy. Defer to follow-up tasks:
Use your search tools to find common issues:
| What to Find | Search Pattern | File Type |
|---|---|---|
| Hardcoded colors | #[0-9A-Fa-f]{6,8} | *.axaml |
| Inline font sizes | FontSize="[0-9] | *.axaml |
| Hardcoded backgrounds | Background="# | *.axaml |
| ResourceDictionary files | ResourceDictionary | *.axaml |
| Avalonia version | PackageReference.*Avalonia | *.csproj, *.props |
| Missing x:DataType (v12) | <UserControl or <Window without x:DataType | *.axaml |
| ViewModel coupling | ViewModel | *.cs in Controls/ |
| Accessibility gaps | AutomationProperties | *.axaml |
| Custom navigation (v12) | INavigationService|NavigationService | *.cs |
For detailed patterns and implementation guidance, consult:
references/design-tokens.md — Complete token organization with AXAML examples (v11 and v12)references/project-structure.md — Detailed folder layouts for small and large projectsreferences/migration-guide.md — Step-by-step migration phases with templates and v12 API changesSubjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations like EF Core migrations or deploys), or any time a confident output would be cheaper to verify now than to debug later.
Delivers .NET/C# changes incrementally — thin vertical slices with dotnet build + dotnet test verification between each. Use when implementing any feature that touches more than one project or assembly. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
Instruments .NET/C# code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting to an ASP.NET Core / Blazor / worker / desktop app. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Hardens .NET/C# code against vulnerabilities — input validation (FluentValidation), EF Core parameterization, ASP.NET Core Identity / JWT bearer / policy-based authz, Data Protection, antiforgery, user-secrets + Key Vault, `dotnet list package --vulnerable`. Use when handling user input, authentication, data storage, or external integrations in ASP.NET Core, Blazor, or Avalonia/MAUI apps that talk to an API.
Drives .NET/C# development with tests — RED/GREEN/REFACTOR with xUnit (v2 or v3) or MSTest, the Prove-It Pattern for bug fixes, the test pyramid with `WebApplicationFactory` for integration and `Playwright`/`Avalonia.Headless` for E2E. Supports both VSTest and Microsoft.Testing.Platform (MTP) runners. Use when implementing any logic, fixing any bug, or changing any behavior.