Dotnet Ui

Organization

novotnyllc

dotnet-ui

Builds .NET UI apps across Blazor (Server, WASM, Hybrid, Auto), MAUI (XAML, MVVM, Shell, Native AOT), Uno Platform (MVUX, Extensions, Toolkit), WPF (.NET 8+, Fluent theme), WinUI 3 (Windows App SDK, MSIX, Mica/Acrylic, adaptive layout), and WinForms (high-DPI, dark mode) with JS interop, accessibility (SemanticProperties, ARIA), localization (.resx, RTL), platform bindings (Java.Interop, ObjCRuntime), and framework selection. Spans 20 topic areas. Do not use for backend API design or CI/CD pipelines.

Overview

Publisher	novotnyllc
Repository	`dotnet-artisan`
Skill name	`dotnet-ui`
Stars	235
Forks	14
Bundled files	21
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
21 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by novotnyllc on GitHub. Read the source before you install it.

Installation

Install the Dotnet Ui AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-ui
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-ui

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/novotnyllc/dotnet-artisan.git /tmp/dotnet-artisan
mkdir -p .claude/skills
cp -r /tmp/dotnet-artisan/plugins/dotnet-artisan/skills/dotnet-ui .claude/skills/dotnet-ui

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dotnet Ui in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dotnet Ui on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dotnet Ui is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

dotnet-ui

Overview

.NET UI development across Blazor, MAUI, Uno Platform, WPF, WinUI 3, and WinForms. This skill covers framework selection, component architecture, XAML patterns, MVVM, platform-specific deployment, accessibility, and localization. Each framework area has a dedicated companion file with deep guidance.

Routing Table

Topic	Keywords	Description	Companion File
Blazor patterns	hosting model, render mode, routing, streaming, prerender	Hosting models, render modes, routing, streaming, prerendering, AOT-safe patterns	references/blazor-patterns.md
Blazor components	lifecycle, state, JS interop, EditForm, QuickGrid	Lifecycle methods, state management, JS interop, EditForm, QuickGrid	references/blazor-components.md
Blazor auth	AuthorizeView, Identity UI, OIDC flows	Login/logout flows, AuthorizeView, Identity UI, OIDC, role and policy auth	references/blazor-auth.md
Blazor testing	bUnit, rendering, events, JS mocking	bUnit component rendering, events, cascading params, JS interop mocking	references/blazor-testing.md
MAUI development	project structure, XAML, MVVM, platform services	Project structure, XAML/MVVM patterns, Shell navigation, platform services	references/maui-development.md
MAUI AOT	iOS/Catalyst, Native AOT, trimming	iOS/Catalyst Native AOT pipeline, size/startup gains, library compatibility	references/maui-aot.md
MAUI testing	Appium, XHarness, platform validation	Appium 2.x device automation, XHarness, platform validation	references/maui-testing.md
Uno Platform	Extensions, MVUX, Toolkit, Hot Reload	Extensions ecosystem, MVUX pattern, Toolkit controls, Hot Reload	references/uno-platform.md
Uno targets	WASM, iOS, Android, macOS, Windows, Linux	Per-target guidance for WASM, iOS, Android, macOS, Windows, Linux	references/uno-targets.md
Uno MCP	tool detection, search-then-fetch, init	MCP tool detection, search-then-fetch workflow, init rules, fallback	references/uno-mcp.md
Uno testing	Playwright WASM, platform patterns	Playwright for WASM, platform-specific test patterns, runtime heads	references/uno-testing.md
WPF modern	Host builder, MVVM Toolkit, Fluent theme	Host builder, MVVM Toolkit, Fluent theme, performance, modern C#	references/wpf-modern.md
WPF migration	WPF/WinForms to .NET 8+, UWP to WinUI	WPF/WinForms to .NET 8+, UWP to WinUI, Upgrade Assistant	references/wpf-migration.md
WinUI	Windows App SDK, XAML, MSIX/unpackaged	Windows App SDK, x:Bind, x:Load, MSIX/unpackaged, UWP migration	references/winui.md
WinForms	high-DPI, dark mode, DI, modernization	High-DPI scaling, dark mode, DI patterns, modernization	references/winforms-basics.md
Accessibility	SemanticProperties, ARIA, AutomationPeer	SemanticProperties, ARIA attributes, AutomationPeer, per-platform testing	references/accessibility.md
Localization	.resx, IStringLocalizer, pluralization, RTL	.resx resources, IStringLocalizer, source generators, pluralization, RTL	references/localization.md
WinUI controls/styling	CommandBar, GridView, adaptive triggers, Mica, system brushes, icons	WinUI control selection, adaptive layout, theming, materials, typography	references/winui-controls-styling.md
UI chooser	framework selection decision tree	Decision tree across Blazor, MAUI, Uno, WinUI, WPF, WinForms	references/ui-chooser.md
Platform bindings	Java.Interop, ObjCRuntime, Android AAR, iOS XCFramework, Slim Binding	Custom native SDK bindings for Android and Apple platforms	references/platform-bindings.md

Scope

Blazor (Server, WASM, Hybrid, Auto) hosting models and components
MAUI mobile/desktop development and Native AOT
Uno Platform cross-platform development and MCP integration
WPF on .NET 8+ and migration from .NET Framework
WinUI 3 / Windows App SDK
WinForms modernization (high-DPI, dark mode, DI)
Accessibility across all UI frameworks
Localization (.resx, IStringLocalizer, pluralization, RTL)
UI framework selection decision tree

Out of scope

Server-side auth middleware and API security configuration -- see dotnet-api
Non-UI testing strategy (unit, integration, E2E architecture) -- see dotnet-testing
Cross-framework UI test patterns (page objects, selectors) -- see dotnet-testing
Playwright browser automation (non-framework-specific) -- see dotnet-testing
Backend API patterns and architecture -- see dotnet-api
Native AOT compilation (non-MAUI) -- see dotnet-tooling
Console UI (Terminal.Gui, Spectre.Console) -- see dotnet-tooling

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dotnet Ui AI skill do?

Why use Dotnet Ui on TypingMind?

Because you install it once and use it with any model. Dotnet Ui is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dotnet Ui in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/novotnyllc/dotnet-artisan/tree/main/plugins/dotnet-artisan/skills/dotnet-ui. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dotnet Ui?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dotnet Ui?

As many as you like. As long as a model supports skills, you can use Dotnet Ui with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dotnet Ui AI skill free?

Yes. It is published on GitHub by novotnyllc under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

dotnet-ui

Overview

Routing Table

Scope

Out of scope

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now