Uno Platform
This skill is a map. It tells you which domain skill to load for a task and lists the rules every Uno Platform change must respect. Do not write code from this file alone: load the domain skill and its reference first, then ground details in the docs.
Pick the domain skills
Most real requests touch two or three domains. Load every one that applies.
| The request involves | Load |
|---|---|
| Loading data, binding input, Models, feeds, states, commands, lists, selection, paging, in an MVUX app or a new app | uno-mvux |
| Pages, routes, back navigation, dialogs, tab bars, navigation drawers, passing data between pages, app shell | uno-navigation |
Uno Toolkit controls (TabBar, NavigationBar, CardContentControl, Chip, DrawerControl, SafeArea, AutoLayout, LoadingView, ShadowContainer, and more) or its attached-property extensions |
uno-toolkit |
| Colors, brushes, typography, Material Design 3, the Simple theme, dark mode, restyling controls, theme resource keys | uno-themes |
| Login, sign-in and sign-out, user accounts, tokens on API calls, Microsoft Entra ID (MSAL), OpenID Connect, protected pages | uno-authentication |
Calling a web API or the template's server project, OpenAPI/Swagger documents, generated Kiota clients (HttpKiota, AddKiotaClient, Content/Client), the API's base URL |
uno-kiota |
| Verifying the running app: inspecting the visual tree, clicking through flows, screenshots, assertions (the Uno App MCP, or the platform accessibility tree for Release builds) | uno-testing |
Worked examples:
- "Add a products page that lists items from our API with a bottom tab" →
uno-navigation(tab shell, route),uno-mvux(IListFeed<T>+FeedView),uno-toolkit(TabBar),uno-themesif styling is mentioned. - "The card on the dashboard looks flat, make it match Material" →
uno-toolkit(CardContentControl),uno-themes(Material brushes). - "Check that the login form shows an error on bad credentials" →
uno-testing, withuno-mvuxif the form logic also needs changes.
Project-wide rules
- Feature switches live in
<UnoFeatures>in the project file (for example<UnoFeatures>Material;Navigation;Toolkit;MVUX</UnoFeatures>). Add the feature there instead of adding raw NuGet package references; the Uno SDK resolves versions. - Keep the app's presentation pattern. An app with
Mvvmin<UnoFeatures>or CommunityToolkit.Mvvm ViewModels (ObservableObject,[RelayCommand]) stays MVVM: write ViewModels with CommunityToolkit.Mvvm, load only the UI hubs (uno-navigation,uno-toolkit,uno-themes,uno-testing), and do not loaduno-mvuxor introduce MVUX unless the user asks for a migration. MVUX is the default only for new apps. - The XAML dialect is WinUI 3. Use
Microsoft.UI.Xamltypes andx:Bind/Bindingas in WinUI, except on MVUX pages: bind the Model surface with{Binding}, notx:Bind. The templates, the docs, and Chefs all use{Binding};x:Bindneeds a typed property on the page for the generated ViewModel, and record-typed states are exposed as a generatedBindable<Name>ViewModelclass with a private setter (opt out with[Value]; simple-typed states are plain properties), so a TwoWayx:Bindto a record state fails at build. Do not use WPF, UWP-only, or Xamarin.Forms/MAUI syntax. - Toolkit and Extensions namespaces are
xmlns:utu="using:Uno.Toolkit.UI",xmlns:uen="using:Uno.Extensions.Navigation.UI", andxmlns:mvux="using:Uno.Extensions.Reactive.UI". - Prefer platform controls over hand-built approximations. A rounded
Borderwith a background is a card, so useCardContentControl; a row of buttons that switches views is aTabBar; a list with add/remove is anIListState<T>. The domain skills spell these out. - Ground API details in the docs, not memory. Call
uno_platform_docs_search(...), thenuno_platform_docs_fetch(sourcePath="…")with thesourcePathfrom a result. Never pass a URL,.htmllink, or hand-built path. Uno APIs change between releases and the docs MCP is version-correct. - Hot Design and Hot Reload questions have no hub of their own:
uno-testingcovers howMainWindow.UseStudio()interacts with an app under test; for everything else search the docs. - Verify before finishing. Use
uno-testing(the Uno App MCP on Debug builds, the platform accessibility tree on Release builds) to confirm the change renders and behaves correctly rather than declaring success from the code alone.
New app scaffolding
For a new project, the typical stack this plugin supports is MVUX + Navigation + Toolkit with the Simple theme, which is what dotnet new unoapp -preset recommended generates; use Material when the brief asks for Material Design. An app created with -preset blank uses Fluent and has no SimpleTheme or MaterialTheme, so no semantic brush, typography, or style key from uno-themes resolves there: use the WinUI resources, or add a theme only with the user's consent. If the user asks for MVVM, use Mvvm instead of MVUX and skip uno-mvux. If users must sign in, add -auth to the template command and load uno-authentication. If the app calls a web API, load uno-kiota; the preset already sets up Kiota. Read uno-navigation (references/setup.md and one shell template), uno-mvux (references/overview.md), and uno-toolkit (references/getting-started.md) in that order, then build the shell before individual pages.