AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

winui-app

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.

Original source
openai
License
Apache-2.0
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--winui-app at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 18

references/performance-diagnostics-and-responsiveness.md


title: Performance, Diagnostics, and Responsiveness priority: HIGH tags: performance, responsiveness, ui-thread, wpr, wpa, diagnostics sources:

  • https://learn.microsoft.com/windows/apps/performance/winui-perf
  • https://github.com/microsoft/WinUI-Gallery

What This Reference Is For

Use this file when the user reports sluggish WinUI behavior, dropped frames, long startup, or laggy scrolling and layout.

Prefer

  • Keeping the UI thread free for layout, rendering, and input.
  • Simpler visual trees and lighter templates.
  • Virtualization-friendly controls and item layouts.
  • Measurement before optimization when the issue is not obvious.

Avoid

  • Doing expensive I/O or CPU work directly on the UI thread.
  • Deeply nested XAML trees without a concrete benefit.
  • Re-templating controls in ways that dramatically increase layout work.
  • Guessing at performance causes without profiling.

Guidance

  • Favor platform controls and layouts that virtualize well for long lists.
  • Defer or background heavy work when it does not need to block interaction.
  • Reduce unnecessary layout invalidation and repeated measure/arrange churn.
  • Use WPR and WPA with the XAML Frame Analysis plugin for frame-level investigations.
  • Treat slow-frame findings as a clue to UI-thread overload, not as a reason to micro-optimize blindly.

Sample and Source Anchors

  • Learn winui-perf.md
  • WinUI Gallery pages that demonstrate adaptive UI and complex controls without excessive custom infrastructure

Review Checklist

  • Is heavy work running off the UI thread where possible?
  • Are large collections using an appropriate items control?
  • Is the visual tree no more complex than it needs to be?
  • Has profiling been used before claiming a fix?