windows-design

Guide Windows desktop app design across WinUI, Tauri, and Electron tracks.

23|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/f0d010c/stark --skill windows-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-design
Source: https://github.com/f0d010c/stark/tree/main/skills/windows-design
Command: npx skills add https://github.com/f0d010c/stark --skill windows-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create Windows desktop applications tailored to different design tracks, ensuring optimal user experience and adherence to Windows UI guidelines.

Core Features & Use Cases

  • Track Selection Guidance: Guides users to choose between system-like, branded, Tauri, or Electron app styles before development.
  • UI Design Briefing: Provides detailed UI and architecture advice based on Windows design standards, including typography, layout components, and idioms.
  • Platform Compatibility Recommendations: Advises on native WinUI 3, branded surface, or web-based frameworks, highlighting trade-offs and fidelities.
  • Example: A developer wants a native Windows editor—this Skill will specify WinUI 3 requirements and suggest appropriate controls and theming.

Quick Start

Ask the user about their target Windows app style and follow guidance on design patterns, controls, and best practices.

Frequently Asked Questions about windows-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a Windows desktop app with native UI guidelines?

Design Windows desktop apps by selecting an appropriate UI track and adhering to Windows UI principles, typography, and layout idioms. The Skill provides detailed design briefings to ensure optimal native user experience and platform compliance.

Should I use Electron, Tauri, or WinUI 3 for my Windows app architecture?

Choosing between WinUI 3, Tauri, and Electron depends on your desired fidelity and branding. WinUI 3 offers a system-like native experience, whereas Tauri and Electron provide web-based frameworks with distinct trade-offs in performance and design surface.

What Windows UI controls and design patterns fit a native desktop editor?

For a native Windows editor, WinUI 3 requirements specify appropriate controls, theming, and design patterns. The Skill identifies necessary components and provides architecture advice based on Windows design standards to ensure idiomatic implementation.

How do I plan the UI track for a branded Windows desktop application?

Plan a branded Windows desktop application by evaluating platform compatibility recommendations across native, branded, and web-based surfaces. This process highlights trade-offs and fidelities to help you select the correct framework style before development begins.

When should I not use a web-based framework for Windows app design?

Avoid web-based frameworks like Electron or Tauri when your app requires strict adherence to system-like native idioms and deep Windows UI integration. In these cases, a native framework like WinUI 3 is necessary to meet design language standards.

Does Windows desktop app design guidance cover layout components and typography?

Windows desktop app design guidance comprehensively covers typography, layout components, and native idioms. It provides detailed architecture advice to ensure your application adheres to Windows UI guidelines across different selected tracks.