What problem does it solve? WinUI 3 code can compile and pass UI tests while still containing fragile patterns — missing x:Bind modes, hardcoded colors, absent AutomationIds, UI-thread blocking, or MVVM violations — that only surface as bugs, accessibility failures, or performance problems later. This Skill provides a structured pre-commit review checklist that catches these issues before they ship. ## Core Features & Use Cases - Checklist-Driven Review: Systematic checks across MVVM compliance, x:Bind correctness, accessibility, theming, security, performance, and globalization, each with concrete pass/fail criteria. - Roslyn Analyzer Integration: Explains how the Microsoft.WindowsAppSDK.Analyzers diagnostics (WUI0xxx–WUI4xxx) complement manual review and how to surface them in builds. - Detailed Rule Reference: Ships a references/quality-rules.md file with code examples for x:Phase, PasswordVault, DPAPI, WebView2 hardening, x:Uid localization, RTL layout, and naming conventions. - Use Case: Before committing a new settings page in a WinUI 3 app, run this review to catch a {Binding} that should be {x:Bind}, a hardcoded #FF0000 brush, and a missing AutomationProperties.AutomationId on a button. ## Quick Start Review my WinUI 3 project's XAML and C# files for MVVM, binding, accessibility, theming, security, and performance issues and report findings with severity and suggested fixes.
