Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/windows-design
Use when the user asks for a Windows app, Win11/Win12 UI, XAML, Fluent design, WinUI, WPF, PowerToys-style tool, Microsoft Store app, desktop utility, admin tool, music/photo/creative app, Tauri desktop, Electron desktop, or any Windows desktop deliverable. Builds Windows apps across system-like WinUI 3, branded WinUI 3, Tauri 2, and Electron while preserving UX decisions, desktop archetype, originality seed, layout sketch, state coverage, Fluent/Mica rules, and motion restraint. ALWAYS ask whic
Passed 22 of 23 test cases with the skill, and 17 of 23 without it.
and 3 more in the full report
5 fixed17 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We decided on Track 3 (Tauri 2 + React) for our Windows utility. What trade-off regarding native visual fidelity should be communicated to the team?
| Checked | Without skill | With skill |
|---|---|---|
| notes that WebView2 font rendering may look subtly off versus native WinUI 3 | Missed | Passed |
The instructions your model reads when the skill loads.
Windows desktop has four distinct tracks. Each has different visual ceilings, different cost. Ask the user which one before any code. Do not default.
Present these four options verbatim. Do not pick for them.
Which track do you want for this app?
1. System-like native (WinUI 3 strict) — feels like Settings/Calculator/Notepad. Best for: productivity utilities, internal tools, system panels. Visual ceiling: medium. Binary ~30MB. Users who care: Windows power users, IT admins. Examples: PowerToys, Snipping Tool, Sound Recorder.
2. Branded native (WinUI 3 + branded Fluent) — native chrome (Mica, Snap Layouts, ThemeResource auto dark/light/HC) but bespoke content surface (custom accent, custom display font, hero atmospheres, magazine layouts). Best for: consumer apps that want fit-in and identity. Visual ceiling: high but XAML-bound. Binary ~30MB. Examples: Apple Music for Windows, Files (community), Microsoft Photos rewrite, DevHome.
3. Tauri 2 + React/Tailwind/Motion — same React code as Electron but uses Windows' built-in WebView2 instead of bundled Chromium. Full visual freedom (mesh gradients, custom motion, real imagery, anything CSS can do). Binary ~5–10MB. RAM ~30–80MB. Mica still available via Tauri API. Examples: Cap, Spacedrive, ClashVerge, Pot.
4. Electron + React/Tailwind/Motion — bundles full Chromium. Same dev experience as Tauri but heavier. Binary ~150–250MB. RAM ~300–500MB. Largest ecosystem, every dev knows it. Examples: Spotify, Discord, VSCode, Slack, Notion, Figma desktop, Claude desktop, ChatGPT desktop.
Which? Or describe priorities (binary size, visual ambition, brand vs fit-in) and I'll pick.
If the user has already given enough signal in the brief (e.g. "I want a system tray utility" → 1; "I want it to look like Awwwards site" → 3; "Spotify-style" → 3 or 4), state your pick + reasoning in one sentence and proceed. But if ambiguous, ask.
| Track | Reference docs | Default stack |
|---|---|---|
| 1. System-like WinUI 3 | ../../references/fluent-design.md | WinUI 3 + current stable Windows App SDK + CommunityToolkit.Mvvm + SettingsControls |
| 2. Branded WinUI 3 | ../../references/fluent-design.md + ../../references/branded-fluent.md | Same as 1 + custom accent override + embedded display font + bespoke surfaces |
| 3. Tauri 2 + Web | ../../references/web-fonts.md + ../../references/web-motion.md + ../../references/web-bans.md + ../../references/awwwards-ceiling.md | React 19 + Tailwind v4 + Motion (motion.dev) + Tauri 2 shell |
| 4. Electron + Web | Same as 3 | React 19 + Tailwind v4 + Motion + Electron shell + electron-builder |
For tracks 3 and 4, the web design rules from web-design SKILL apply — same anti-slop ban list, same typography curation, same aesthetic direction discipline.
test cases passed, vs 17 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.