Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill swiftui-performance-audit100
Does it follow best practices?
Validation for skill structure
Heavy body computation anti-patterns
Formatter in body
100%
100%
Formatter cache fix
100%
100%
Inline sort in ForEach
100%
100%
Sort precomputation fix
100%
100%
Computed filter on every eval
100%
100%
Filter cache fix
100%
100%
Impact ordering
100%
100%
Proposed fix per issue
100%
100%
NumberFormatter issue
100%
100%
Body work explanation
100%
100%
Without context: $0.2331 · 1m 18s · 6 turns · 7 in / 4,969 out tokens
With context: $0.4238 · 2m 8s · 15 turns · 96 in / 7,110 out tokens
Unstable identity and broad state dependencies
Broad observable dependency
100%
100%
Granular view model fix
50%
100%
Top-level conditional swapping
100%
100%
Stable base view fix
80%
100%
Narrow state scope
90%
90%
FavoriteTagView fan-out
70%
60%
Avoiding environment for fast-changing values
10%
70%
Impact ordering
100%
100%
Proposed fix per issue
100%
100%
Update fan-out explanation
90%
100%
Without context: $0.3109 · 1m 58s · 7 turns · 8 in / 6,810 out tokens
With context: $0.4978 · 3m 8s · 14 turns · 13 in / 9,236 out tokens
Image decoding and layout thrash
Main-thread image decode
100%
100%
Off-thread decode fix
100%
100%
Image downsampling
0%
0%
GeometryReader layout thrash
100%
100%
Reduce GeometryReader fix
100%
100%
Top-level conditional swapping
0%
100%
Stable overlay fix
0%
100%
Formatter allocation in overlay
100%
100%
Formatter cache fix
100%
100%
Impact ordering
100%
100%
Without context: $0.3076 · 1m 37s · 9 turns · 10 in / 5,954 out tokens
With context: $0.4788 · 2m 33s · 14 turns · 13 in / 8,533 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.