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
• connecting desktop applications with backend agent services and building AI agents with .NET

Workflow

1. Confirm Windows-only scope — WPF is Windows-only even when the wider .NET stack is cross-platform
2. Apply MVVM pattern — keep views dumb, logic in ViewModels, use commands
3. Manage data binding explicitly — choose correct binding modes, validate at runtime
4. Use styles and templates deliberately — keep UI composable, avoid page-specific hacks
5. Handle threading correctly — use Dispatcher for UI updates, async/await for long operations
6. Validate both designer and runtime — XAML composition failures often surface only at runtime

Deliver

• cleaner WPF views and view-model boundaries
• safer binding and threading behavior
• migration guidance grounded in actual Windows constraints
• MVVM pattern with testable ViewModels

Validate

• binding and command flows are explicit
• code-behind is not carrying hidden business logic
• Windows-only assumptions are acknowledged
• threading and dispatcher usage is correct
• styles and resources are properly organized

Documentation

References

Related skills