performance
/performance
Make a Windows app fast by measuring hangs, stutter, CPU, memory, and UI stalls, then moving work off the UI thread and onto the GPU. Use when the app freezes, a shortcut feels slow, dragging stutters, memory grows, or the user asks to profile.
- Author
- MinnThikeTunn ↗
- Repository
- Phan-Tee ↗
- Licence
- MIT
- Last repository change
- 02.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Make a Windows app fast by measuring hangs, stutter, CPU, memory, and UI stalls, then moving work off the UI thread and onto the GPU. Use when the app freezes, a shortcut feels slow, dragging stutters, memory grows, or the user asks to profile.
Original author description
Make a Windows app fast by measuring hangs, stutter, CPU, memory, and UI stalls, then moving work off the UI thread and onto the GPU. Use when the app freezes, a shortcut feels slow, dragging stutters, memory grows, or the user asks to profile.
How it works
- The loop
- The rules that fix most problems
- Done when
SKILL.md preview
--- name: performance description: Make a Windows app fast by measuring hangs, stutter, CPU, memory, and UI stalls, then moving work off the UI thread and onto the GPU. Use when the app freezes, a shortcut feels slow, dragging stutters, memory grows, or the user asks to profile. --- # Performance Fast means two numbers: the first frame after a key press shows in under 100 ms, and nothing on the UI thread blocks for more than 50 ms. Every change starts and ends with a **measurement**, so you know it helped. ## The loop ```text reproduce -> measure (release build) -> find the line -> fix -> measure again -> commit with numbers ``` 1. **Reproduce.** Write the exact steps, or run a probe command that logs the elapsed time of each step. 2. **Measure the release build.** Debug builds have heavy diagnostics and point at the wrong code. 3. **Find the line:** - App freezes / UI stalls: `dotnet-trace collect --process-id <PID>` - Memory growth / leaks: `dotnet-dump collect --process-id <PID>` - Rendering hitches: Inspect Composition Frame rates. 4. **Fix with the matching recipe.** 5. **Measure again.** Put before and after in the commit message: "List filter opens in 25 ms, was 420 ms". ## The rules that fix most problems - **UI thread does UI only.** File I/O, database queries, image decoding, and OCR must run in background threads (`Task.Run`). - **Show first, work after.** Put the window or panel on screen in the same frame as the key press, then load. Never make the UI wait for the work. - **Virtualize large lists.** Use `ListView` with item virtualization or `ItemsRepeater` so off-screen elements are not instantiated. - **Decode at display size.** Decode images at the exact dimensions they will render at on screen. - **No polling without reason.** Use event-driven APIs (e.g., `AddClipboardFormatListener`) instead of `DispatcherTimer` polling loops. ## Done when UI thread bottlenecks are profiled, memory allocations are reduced, and the app sustains 60 FPS without frame drops.
Files in this package (4)
- SKILL.md 2 KB
- gpu-media.md 1 KB
- recipes.md 1 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · MinnThikeTunn/Phan-Tee | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| davila7/claude-code-templates | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| arxdsilva/ai-loops | 100 | MIT |
Database snapshot: 13.11.2026 · package version 542c1636e6a6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90Android Performance
Measure and improve Android app performance on the phone: startup time, jank, memory, baseline profiles, R8 and main-thread work. Use when the app feels slow or the user asks for optimization. - 100performance-craft
Measure, diagnose and fix performance across web, mobile apps and their backends - load time, Core Web Vitals (LCP/INP/CLS), bundle size, jank, slow lists, app launch, hangs, memory, battery, slow APIs, N+1 queries, caching, database and network. Use for broad requests like… - 100performance-profiling
Finds and fixes backend and application performance problems by measuring first - define the target metric, reproduce under realistic load, profile CPU, memory, I/O and locks, fix the biggest bottleneck, re-measure, and add a regression guard. Use when code or a service is slow,… - 100systems-performance
Reason about how code really runs on hardware - memory and caches, CPU, concurrency, I/O and the operating system - to find and fix slowness, high memory use, contention and race conditions. Use whenever code is slow, uses too much memory, stalls under load, behaves differently… - 100threejs-performance
Measuring and optimizing three.js speed: render statistics, memory counters, fewer draw calls via merging, instancing, batching and LOD, fill rate, shadows, CPU work per frame, shader stalls and GPU compute for particles, WebGL or WebGPU with TSL. Use when a scene is slow, janks or exceeds memory. - 100performance-profiling
Guide performance profiling for Apple platform apps with Instruments, Xcode diagnostics, and MetricKit. Use when investigating app hangs, stutters, high CPU, memory leaks, memory growth, OOM crashes, slow launch, battery drain, thermal issues, App Store performance readiness, or…