skilld
All skills
openai avatar

/winui-app

@c207989 official
by openaiopenai/skills28k stars
1,891

Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/winui-app

This session only. Nothing lands on disk.

referencesaccessibility-input-and-localization.md

≈507 tokens on demand. Your agent reads this file only when SKILL.md points to it.

What This Reference Is For

Use this file for keyboard accessibility, Narrator support, automation properties, input parity, high contrast, and localization-ready UI.

Prefer

  • Accessible names, help text, and landmarks for meaningful UI elements.
  • Full keyboard reachability for the main workflow.
  • High-contrast-safe visuals.
  • Localizable strings and layouts that tolerate growth.
  • Equal support for mouse, touch, pen, and keyboard where the platform expects it.

Avoid

  • Icon-only interactions without accessible naming.
  • Focus traps, hidden tab stops, or keyboard-only dead ends.
  • Hard-coded strings in XAML or code-behind that block localization.
  • Text layouts that collapse when strings expand.

Guidance

  • Use automation properties intentionally.
  • Preserve visible focus and logical tab order.
  • Verify context menus, flyouts, and dialogs by keyboard as well as mouse.
  • Respect text scaling, contrast changes, and RTL where relevant.
  • Keep touch targets and spacing usable on both mouse and touch hardware.

WinUI Gallery Anchors

  • Accessibility-related control samples
  • Automation helper patterns in shell code
  • Standard WinUI controls that already expose useful accessibility behavior

Review Checklist

  • Can a keyboard-only user complete the task?
  • Does Narrator have enough information to describe the important UI?
  • Does the experience stay legible in high contrast?
  • Are strings and layout ready for localization and RTL growth?

Source: SKILL.md on GitHub

Third-party checks

No alerts17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill provides guidance and scaffolding patterns for building WinUI 3 desktop applications with the Windows App SDK. It includes standard platform configuration and setup mechanisms that leverage official Windows tools. While it executes configuration scripts to configure the local environment, these are implemented via native tools such as WinGet according to official Microsoft workflows.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer6mo

    5/20 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at c207989. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 7 months ago

Topics

  • winui
  • csharp
  • windows-app-sdk
  • desktop
  • xaml
  • visual-studio
  • winget
  • theming
  • accessibility
  • responsive-design

README badge

README badge for openai/skills/winui-app

What it does

Bootstraps and develops WinUI 3 desktop applications in C# using the Windows App SDK, with guidance for environment setup, project scaffolding, XAML patterns, controls, navigation, theming, and deployment. Use this skill when creating a new app, preparing a machine for WinUI development, or troubleshooting XAML compilation and startup issues.

Generated from the current SKILL.md.

Frequently asked

Does this skill work with C++ or only C#?
The skill is built around C# and the Windows App SDK. C++ or C++/WinRT is mentioned only when the difference is material to the task.
Can I use this skill to set up an unpackaged app instead of a packaged one?
Yes. The skill supports both packaged and unpackaged app models. You can pass the `--unpackaged` flag to `dotnet new winui`, or the skill will default to packaged for Store-like workflows and unpackaged for CLI build-and-run loops.
What if my machine isn't ready for WinUI development yet?
The skill includes a bundled WinGet configuration (`config.yaml`) that installs Visual Studio Community 2026, enables Developer Mode, and adds the required Windows App SDK C# components. For diagnostics-only audits without machine changes, the skill provides manual verification guidance instead.
Does this skill handle third-party component libraries or only native WinUI controls?
The skill favors native WinUI controls and Fluent styling first. It uses the CommunityToolkit only when built-in controls do not cover the need cleanly, and avoids inventing custom component libraries unless you explicitly request them.

Generated from the current SKILL.md. These answers refresh after source changes.