Build and modernize WPF applications on .NET with correct XAML, data binding, commands, threading, styling, and Windows desktop migration decisions. USE FOR: working on WPF UI, MVVM, binding, commands, or desktop modernization; migrating WPF from .NET Framework to .NET; integrating newer Windows capabilities into a WPF app. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build,
NewMaintained
Automatic
◆Frontend / UI pack
Last verified 8/19/2026
What it changes
Passed 13 of 22 test cases with the skill, and 13 of 22 without it.
Without skill59%
With skill59%
Checks it passed that the model alone missed
Sets x:CompileBindings to True in the XAML markup.
1 fixed12 passed either way8 still failing1 broke
Pass-rate lift
0 pp
Tokens
+128%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/19/2026v213 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
We are migrating a WPF project to modern .NET 8 and want to improve XAML binding performance and catch binding path errors at compile time instead of runtime. What XAML attribute enables this?
What was checked, without and with the skill
Checked
Without skill
With skill
Sets x:CompileBindings to True in the XAML markup.
Missed
Passed
Explains compile-time validation benefits for WPF XAML bindings.
Passed
Passed
case-19 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md406 lines3 files
WPF
Trigger On
working on WPF UI, MVVM, binding, commands, or desktop modernization
migrating WPF from .NET Framework to .NET
integrating newer Windows capabilities into a WPF app
implementing data binding, styles, templates, or control customization
anti-patterns.md - Common WPF mistakes and how to avoid them
Workflow
Confirm Windows-only scope — WPF is Windows-only even when the wider .NET stack is cross-platform
Apply MVVM pattern — keep views dumb, logic in ViewModels, use commands
Manage data binding explicitly — choose correct binding modes, validate at runtime
Use styles and templates deliberately — keep UI composable, avoid page-specific hacks
Handle threading correctly — use Dispatcher for UI updates, async/await for long operations
Validate both designer and runtime — XAML composition failures often surface only at runtime
Current Upstream Notes
The August 2026 WPF overview reiterates WPF as a Windows-only desktop UI stack with XAML, data binding, styling, templates, resources, and vector/rich-media composition. Keep WPF-specific guidance separate from WinUI or MAUI unless the task is explicitly a migration or comparison.
WPF exists on both .NET Framework and modern .NET. For modernization work, inventory compatibility constraints and use the current desktop migration guidance before moving project files, interop, deployment, or XAML resource dictionaries.