wpf-best-practices
Best practices for building WPF desktop applications with C# and .NET. Use when working on WPF projects, .NET desktop apps, XAML UI, MVVM architecture, system tray apps, or any C# project using Windows Presentation Foundation.
What this skill does
# WPF Best Practices
You are an expert in C#, .NET, and WPF desktop application development with deep
knowledge of MVVM architecture, dependency injection, async/await patterns, and
Windows desktop integration.
## C# Code Style
### Basic Principles
- Use English for all code and documentation
- Always declare types for variables and functions (parameters and return values)
- Enable nullable reference types project-wide
- Use file-scoped namespaces โ no braces, no nesting
- Write concise, maintainable code โ avoid over-engineering
### File-Scoped Namespaces
Always use file-scoped namespaces:
```csharp
namespace MyApp.Services;
public class SettingsService
{
// No extra indentation level
}
```
### Nullable Reference Types
Always enabled in csproj (`<Nullable>enable</Nullable>`):
```csharp
public class AppNotification
{
public string Title { get; set; } = ""; // Non-nullable with default
public string Message { get; set; } = "";
public string? Channel { get; set; } // Explicitly nullable
public string[]? Tags { get; set; }
}
```
### Naming Conventions
- **PascalCase** for types, interfaces, properties, methods, events, constants
- **camelCase** for local variables and parameters
- **_camelCase** for private fields
- **IPascalCase** for interfaces (prefix with `I`)
- **UPPERCASE** for environment variables only
- Prefix boolean properties/fields with `Is`, `Has`, `Can`, `Should`
```csharp
public class ConnectionService
{
private readonly ILogger _logger;
private readonly string _serverUrl;
private bool _isConnected;
public bool IsConnected => _isConnected;
public bool CanReconnect { get; private set; }
}
```
### Modern C# Features
Use switch expressions:
```csharp
public string StatusIcon => Status switch
{
ConnectionStatus.Connected => "๐ข",
ConnectionStatus.Connecting => "๐ก",
ConnectionStatus.Disconnected => "๐ด",
_ => "โช"
};
```
Use range/slice operators:
```csharp
private static string Capitalize(string s) =>
string.IsNullOrEmpty(s) ? s : char.ToUpper(s[0]) + s[1..];
```
Avoid redundant default initializers:
```csharp
// Good
private bool _disposed;
private int _retryCount;
// Bad โ redundant
private bool _disposed = false;
private int _retryCount = 0;
```
---
## Project Structure
```
MyApp/
โโโ MyApp.sln # Solution file
โโโ src/
โ โโโ MyApp/ # Main WPF application
โ โ โโโ App.xaml # Application entry, resource dictionaries
โ โ โโโ App.xaml.cs # DI setup, app lifecycle, crash handlers
โ โ โโโ Views/ # XAML windows and user controls
โ โ โโโ ViewModels/ # MVVM presentation logic
โ โ โโโ Models/ # Data classes and enums
โ โ โโโ Services/ # Business logic (DI singletons)
โ โ โ โโโ Interfaces/ # Service contracts
โ โ โโโ Utilities/ # Helpers (encryption, screen, JSON)
โ โ โโโ Constants/ # App-wide constants
โ โโโ MyApp.Shared/ # Cross-platform shared library
โ โโโ MyApp.Shared.csproj
โโโ tests/
โ โโโ MyApp.Tests/ # xUnit test project
โ โโโ MyApp.Tests.csproj
โโโ .github/
โโโ workflows/ # CI/CD
```
### Project File Configuration
WPF app csproj:
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFramework>net10.0-windows</TargetFramework>
<UseWPF>true</UseWPF>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
</Project>
```
Shared library csproj (cross-platform):
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net10.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
<ItemGroup>
<InternalsVisibleTo Include="MyApp.Tests" />
</ItemGroup>
</Project>
```
---
## MVVM Pattern
### ViewModelBase
Every ViewModel should inherit from a shared base:
```csharp
namespace MyApp.ViewModels;
public abstract class ViewModelBase : INotifyPropertyChanged
{
public event PropertyChangedEventHandler? PropertyChanged;
protected void OnPropertyChanged([CallerMemberName] string? name = null) =>
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs(name));
protected bool SetProperty<T>(ref T field, T value,
[CallerMemberName] string? name = null)
{
if (EqualityComparer<T>.Default.Equals(field, value)) return false;
field = value;
OnPropertyChanged(name);
return true;
}
}
```
Usage:
```csharp
public class MainViewModel : ViewModelBase
{
private string _title = "";
public string Title
{
get => _title;
set => SetProperty(ref _title, value);
}
private bool _isLoading;
public bool IsLoading
{
get => _isLoading;
set => SetProperty(ref _isLoading, value);
}
}
```
### RelayCommand
Use a simple `RelayCommand` for XAML command bindings:
```csharp
namespace MyApp.ViewModels;
public class RelayCommand : ICommand
{
private readonly Action<object?> _execute;
private readonly Func<object?, bool>? _canExecute;
public RelayCommand(Action<object?> execute, Func<object?, bool>? canExecute = null)
{
_execute = execute;
_canExecute = canExecute;
}
public event EventHandler? CanExecuteChanged
{
add => CommandManager.RequerySuggested += value;
remove => CommandManager.RequerySuggested -= value;
}
public bool CanExecute(object? parameter) => _canExecute?.Invoke(parameter) ?? true;
public void Execute(object? parameter) => _execute(parameter);
}
public class RelayCommand<T> : ICommand
{
private readonly Action<T?> _execute;
private readonly Func<T?, bool>? _canExecute;
public RelayCommand(Action<T?> execute, Func<T?, bool>? canExecute = null)
{
_execute = execute;
_canExecute = canExecute;
}
public event EventHandler? CanExecuteChanged
{
add => CommandManager.RequerySuggested += value;
remove => CommandManager.RequerySuggested -= value;
}
public bool CanExecute(object? parameter) =>
_canExecute?.Invoke(parameter is T t ? t : default) ?? true;
public void Execute(object? parameter) =>
_execute(parameter is T t ? t : default);
}
```
### AsyncRelayCommand
For async operations bound to UI:
```csharp
namespace MyApp.ViewModels;
public class AsyncRelayCommand : ICommand
{
private readonly Func<object?, Task> _execute;
private readonly Func<object?, bool>? _canExecute;
private bool _isExecuting;
public AsyncRelayCommand(Func<object?, Task> execute,
Func<object?, bool>? canExecute = null)
{
_execute = execute;
_canExecute = canExecute;
}
public event EventHandler? CanExecuteChanged
{
add => CommandManager.RequerySuggested += value;
remove => CommandManager.RequerySuggested -= value;
}
public bool CanExecute(object? parameter) =>
!_isExecuting && (_canExecute?.Invoke(parameter) ?? true);
public async void Execute(object? parameter)
{
if (_isExecuting) return;
_isExecuting = true;
CommandManager.InvalidateRequerySuggested();
try
{
await _execute(parameter);
}
finally
{
_isExecuting = false;
CommandManager.InvalidateRequerySuggested();
}
}
}
```
### Data Binding in XAML
```xml
<Window x:Class="MyApp.Views.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Title="{Binding Title}">
<Grid>
<TextBlock Text="{Binding StatusText}"
Visibility="{Binding IsLoading,
Converter={SRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.