跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

windows-design

Design rules that make a WinUI 3 app look and feel like a native Windows 11 app, from the Fluent design principles to Mica, the title bar, navigation, command bars, menus, keyboard, type, color, and dark mode. Use when building or reviewing any window, page, command bar, menu, flyout, dialog, or settings page, or when the user asks for a more native, Windows-like, or better designed app.

daveebbelaar · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add daveebbelaar/bawa --skill windows-design

技能说明


name: windows-design description: Design rules that make a WinUI 3 app look and feel like a native Windows 11 app, from the Fluent design principles to Mica, the title bar, navigation, command bars, menus, keyboard, type, color, and dark mode. Use when building or reviewing any window, page, command bar, menu, flyout, dialog, or settings page, or when the user asks for a more native, Windows-like, or better designed app.

Windows design

Microsoft already designed your app. Pick the right WinUI controls, arrange them, and stay out of their way. Use the system first. Add custom design only where WinUI has nothing.

  • The full checklist: design-rules.md. Use it for reviews.
  • Copyable XAML: patterns.md.
  • The Settings page: settings.md.
  • Commands: command bars, menus, context menus, and shortcuts: commands.md.
  • Microsoft's own text on one topic, when a rule here is not enough: the Windows app design pages on Microsoft Learn (learn.microsoft.com/windows/apps/design/), for example controls/navigationview or signature-experiences/materials. The WinUI Gallery app shows every control live.
  • App-wide tokens (colors, radii, motion): call the Skill tool with design-system.
  • How a feature works and what it says (names, flow, dialogs, errors, accessibility): call the Skill tool with ux-design.
  • Spacing, alignment, and the checks that catch misalignment: call the Skill tool with layout-grid.
  • Parts of your own instead of Fluent's: call the Skill tool with design-kit, or design-from-app to match an app the user names.

Fluent principles

Use them as the review lens for every screen (Windows 11 design principles):

  1. Effortless: faster and easier to do what people want, with focus and precision. Cut what does not earn its place.
  2. Calm: quieter, less cluttered, less noisy. Soft materials, rounded corners, motion that informs and never shows off.
  3. Personal: the app fits the person. It follows their theme, accent, text size, and contrast settings.
  4. Familiar: things that look the same work the same. Standard controls, standard shortcuts, standard words.
  5. Complete and coherent: the app feels like part of Windows on every screen, in light, dark, and high contrast, with mouse, keyboard, touch, and pen.

Every screen answers: Where am I? What can I do? Where can I go?

Before you write pages

Write these under ## Design plan in docs/BRIEF.md, or in docs/DESIGN.md when the brief would pass one page:

  1. Archetype: navigation window, single-page tool, tray app, or quick-capture panel. Most personal apps are a navigation window plus one quick-capture entry point. A tray utility is "tray icon + flyout or panels + Settings window": the navigation rules then apply to the Settings window only.
  2. Information architecture: navigation pages, at most two levels.
  3. Command map: every action, where it lives (command bar, context menu, tray menu), and its shortcut.
  4. Empty states: what each page shows before there is data.
  5. Feeling: the one feeling the app aims for (calm, quick, confident). Motion, words, and color all reinforce it.

Entry points first

A Windows utility is used through its small entry points: a global shortcut, the tray icon, Start, a quick panel, drag and drop, the taskbar jump list. Design those first. A to-do app lives in its quick-add panel.

  • Quick capture: one small window with one input, opened by a global shortcut, closed by Esc or Enter.
  • Optimistic UI: on Enter, close and show the result at once. Save in the background. Offer Undo, not a progress ring.

Layout

  • The window: Mica backdrop, ExtendsContentIntoTitleBar with the TitleBar control (app icon, app name, the pane toggle, a search box in the middle when the app has search), and a left NavigationView with Settings at the bottom. No NavigationView when the app has one page.
  • NavigationView pane modes: Left on a wide window. It collapses to a compact rail and then to a hamburger on its own as the window narrows. Keep that behavior.
  • Each page: a title in TitleTextBlockStyle, page commands in a CommandBar on the right of the title row, then content.
  • Content sits on cards (CardBackgroundFillColorDefaultBrush, a 1 epx CardStrokeColorDefaultBrush border, OverlayCornerRadius) over the Mica layer. The window background itself stays Mica.
  • List and detail: a list column (320 epx) and a detail card, or a ListView that opens a detail page on narrow windows.
  • Progressive disclosure: an empty page shows one empty state with the first action. Filters appear once there is content.
  • Spacing from UI/Space.xaml, on a 4 epx grid: 36 epx page margins on the sides, 8 between related controls, 16 between cards in a row, 24 between a title and its content, 32 above a group header. Controls take their height from WinUI (32 epx buttons and boxes), never a fixed height.
  • The minimum window size keeps every page usable. Test it in snapshots by setting the window to the minimum.

Materials

  • Mica on the main window. It tints with the desktop wallpaper and goes flat when the window is inactive. That is expected.
  • Mica Alt (MicaBackdrop Kind="BaseAlt") for windows with tabs in the title bar.
  • Acrylic belongs to transient surfaces: flyouts, menus, tooltips, and a quick panel. WinUI gives flyouts and menus acrylic on their own. Never put acrylic on a page background.
  • Content gets solid card fills, never a backdrop of its own.
  • Never a material on a material: a card on Mica, yes; an acrylic card on Mica, no.

Commands and menus

  • Page commands live in a CommandBar with DefaultLabelPosition="Right" for up to four primary commands, the rest in the overflow. Icons from Segoe Fluent Icons, every one with a label.
  • One accent button (`AccentB
阅读完整来源 ↗