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/motion-animations-and-polish.md


title: Motion, Animations, and Polish priority: MEDIUM tags: motion, animations, transitions, connected-animation, polish sources:

  • https://learn.microsoft.com/windows/apps/design/motion/
  • https://github.com/microsoft/WinUI-Gallery
  • https://github.com/CommunityToolkit/Windows

What This Reference Is For

Use this file when adding polish to a WinUI app through motion, transitions, and subtle animated state changes.

Prefer

  • Motion that clarifies hierarchy, continuity, and state changes.
  • Theme transitions, connected animations, and built-in platform behaviors before custom animation systems.
  • Short, purposeful animations that support the task.

Avoid

  • Decorative animation that delays interaction.
  • Multiple overlapping animations for the same state change.
  • Animation that hides focus, selection, or accessibility state.

Guidance

  • Use transitions to explain where content came from and where it went.
  • Keep entrance and exit motion subtle.
  • Use connected animation when there is a real source-to-destination relationship.
  • Reach for CommunityToolkit animation helpers only when built-in transitions are not enough.

Sample and Source Anchors

  • WinUI Gallery animation, transition, and implicit animation pages
  • Learn motion guidance
  • CommunityToolkit animations package and samples

Review Checklist

  • Does the motion improve clarity?
  • Is the app still responsive while the animation runs?
  • Can the transition be simplified to a built-in WinUI behavior?
  • Does the motion preserve accessibility and input clarity?