Uno Platform
Build cross-platform .NET applications with Uno Platform targeting WebAssembly, iOS...
Install
npx skills add managedcode/dotnet-skills --skill uno-platform -g -a claude-code -y- Repository
- managedcode/dotnet-skills500
- Category
- Testing
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,794 tokens
- Runs scripts
- No, instructions only
What it does
Build cross-platform .NET applications with Uno Platform targeting WebAssembly, iOS, Android, macOS, Linux, and Windows from a single XAML/C# codebase. USE FOR: building cross-platform apps from a single C# and XAML codebase; targeting WebAssembly, iOS, Android, macOS, Linux, and Windows simultaneously; migrating WPF or UWP. 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, test, lint, or validation commands when changes are made.
Uno Platform
Trigger On
- building cross-platform apps from a single C# and XAML codebase
- targeting WebAssembly, iOS, Android, macOS, Linux, and Windows simultaneously
- migrating WPF or UWP applications to cross-platform
- implementing pixel-perfect UI across all platforms
- using WinUI/UWP APIs on non-Windows platforms
Documentation
- Uno Platform Overview
- Getting Started
- Using Uno Platform with WinUI
- Platform-Specific Code
- MVUX Pattern
References
See detailed examples in the references/ folder:
patterns.md, MVUX, XAML, navigation, and performance patterns
Platform Support
| Platform | Rendering | Notes |
|---|---|---|
| Windows | WinUI 3 | Native Windows App SDK |
| WebAssembly | Skia/Canvas | Runs in browser |
| iOS | Skia/Metal | Native iOS app |
| Android | Skia/OpenGL | Native Android app |
| macOS | Skia/Metal | Mac Catalyst or AppKit |
| Linux | Skia/X11 | GTK or Framebuffer |
Workflow
- Choose the right template, Uno Platform offers various templates for different scenarios
- Understand rendering modes, Skia vs native rendering affects performance and fidelity
- Apply MVVM or MVUX patterns, keep views dumb, logic in ViewModels
- Handle platform differences, use conditional XAML or partial classes
- Test on all target platforms, behavior varies across platforms
