home / skills / 404kidwiz / claude-supercode-skills / windows-app-developer-skill

windows-app-developer-skill skill

/windows-app-developer-skill

This skill helps you develop modern Windows desktop apps with WinUI 3 and WPF, guiding MVVM, XAML, and MSIX packaging.

npx playbooks add skill 404kidwiz/claude-supercode-skills --skill windows-app-developer-skill

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.4 KB
---
name: windows-app-developer
description: Expert in building modern Windows applications using WinUI 3, WPF, and the Windows App SDK. Specializes in MSIX packaging, XAML styling, and MVVM architecture.
---

# Windows App Developer

## Purpose
Provides expertise in building modern Windows desktop applications using WinUI 3, WPF, and Windows App SDK. Specializes in XAML-based UI development, MVVM architecture, native Windows integration, and modern packaging with MSIX.

## When to Use
- Building Windows desktop applications with WinUI 3 or WPF
- Implementing MVVM architecture for Windows apps
- Creating XAML layouts and custom controls
- Packaging applications with MSIX
- Integrating with Windows features (notifications, taskbar, system tray)
- Migrating WPF applications to WinUI 3
- Implementing Windows-specific features (jump lists, live tiles)
- Building Microsoft Store-ready applications

## Quick Start
**Invoke this skill when:**
- Building Windows desktop applications with WinUI 3 or WPF
- Implementing MVVM architecture for Windows apps
- Creating XAML layouts and custom controls
- Packaging applications with MSIX
- Integrating with Windows features (notifications, taskbar)

**Do NOT invoke when:**
- Building cross-platform apps → use mobile-developer or electron-pro
- Console applications → use appropriate language skill
- PowerShell GUI → use powershell-ui-architect
- Web applications → use appropriate web skill

## Decision Framework
```
Windows App Task?
├── New Modern App → WinUI 3 with Windows App SDK
├── Existing WPF App → Maintain or migrate to WinUI 3
├── Cross-Platform Priority → Consider .NET MAUI
├── Enterprise Internal → WPF with proven patterns
├── Store Distribution → MSIX packaging required
└── System Integration → P/Invoke or Windows SDK APIs
```

## Core Workflows

### 1. WinUI 3 Application Setup
1. Create project using Windows App SDK template
2. Configure Package.appxmanifest for capabilities
3. Set up MVVM infrastructure (CommunityToolkit.Mvvm)
4. Implement navigation and shell structure
5. Create reusable control library
6. Configure MSIX packaging
7. Set up CI/CD for Store or sideload distribution

### 2. MVVM Implementation
1. Define ViewModels with observable properties
2. Implement commands for user actions
3. Create services for data and business logic
4. Set up dependency injection container
5. Bind Views to ViewModels in XAML
6. Implement navigation service
7. Add design-time data for XAML preview

### 3. MSIX Packaging
1. Configure Package.appxmanifest
2. Define application identity and capabilities
3. Set up visual assets (icons, splash)
4. Configure installation behavior
5. Sign package with certificate
6. Test installation and updates
7. Submit to Microsoft Store or deploy internally

## Best Practices
- Use WinUI 3 for new development, WPF for legacy maintenance
- Implement MVVM strictly for testability and separation
- Use x:Bind for compile-time binding validation
- Leverage Community Toolkit for common patterns
- Package with MSIX for modern installation experience
- Follow Fluent Design System for consistent UX

## Anti-Patterns
- **Code-behind logic** → Move to ViewModels
- **Synchronous UI operations** → Use async/await for I/O
- **Direct service calls from Views** → Go through ViewModels
- **Ignoring DPI awareness** → Test at multiple scale factors
- **Missing capabilities** → Declare required capabilities in manifest

Overview

This skill provides hands-on expertise for building modern Windows desktop applications using WinUI 3, WPF, and the Windows App SDK. It focuses on XAML-based UI, MVVM architecture, native Windows integrations, and MSIX packaging to deliver maintainable, store-ready apps. Use it to design responsive UI, implement robust view-model layering, and prepare apps for distribution and updates.

How this skill works

The skill inspects project goals and recommends a platform (WinUI 3 for new apps, WPF for legacy maintenance) and an architecture based on MVVM. It guides setup steps: project templates, app manifest configuration, dependency injection, navigation, and reusable control libraries. It also provides detailed MSIX packaging flow, signing, and deployment guidance, plus integration patterns for Windows features like notifications and taskbar actions.

When to use it

  • Starting a new Windows desktop app targeting modern Windows UX (choose WinUI 3 + Windows App SDK).
  • Maintaining or migrating an existing WPF application to a modern stack or hybrid approach.
  • Implementing MVVM for testability, design-time data, and separation of concerns.
  • Creating custom XAML controls, styling with Fluent Design, and optimizing DPI/scaling.
  • Packaging and distributing apps using MSIX for Store submission or enterprise sideloading.

Best practices

  • Favor WinUI 3 for new development and WPF for proven legacy scenarios.
  • Implement strict MVVM: keep code-behind minimal and move logic to ViewModels.
  • Use x:Bind where possible for compile-time binding validation and performance.
  • Leverage CommunityToolkit.Mvvm and dependency injection for common patterns.
  • Package with MSIX, sign packages, and test install/update flows across environments.

Example use cases

  • Create a new Mail or Dashboard client with WinUI 3, MVVM, and fluent styling.
  • Migrate a line-of-business WPF app incrementally to WinUI 3 while keeping core logic.
  • Build custom reusable control libraries and theme resources for enterprise apps.
  • Implement taskbar integration, notifications, and app lifecycle handling on Windows.
  • Prepare and publish an app to the Microsoft Store with MSIX packaging and signing.

FAQ

Should I choose WinUI 3 or WPF for a new project?

Choose WinUI 3 for new projects to use the Windows App SDK and Fluent Design; use WPF only if you rely on legacy libraries or long-term enterprise stability.

When is MSIX required?

MSIX is required for Store distribution and recommended for modern, reliable install/update behavior for both Store and enterprise scenarios.