Ios performance debugging
Skill sarveshsea/design-skills/skills/ios-performance-debugging
Diagnose SwiftUI rendering, launch, responsiveness, concurrency, memory, energy, and simulator failures using reproducible traces and before-after evidence.From its SKILL.md
npx -y skills add sarveshsea/design-skills --skill ios-performance-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 235 tokens by cl100k_base, as published. Nobody here has run it
iOS Performance Debugging
Workflow
- Define one reproducible user flow and one metric before changing code.
- Capture device, OS, build configuration, commit, data fixture, and baseline trace.
- Use the narrowest instrument: SwiftUI updates and hitches, Time Profiler, Allocations/Leaks, Network, Energy, or concurrency analysis.
- Correlate the trace to source. Do not optimize from intuition alone.
- Change one ownership, identity, layout, allocation, or scheduling cause at a time.
- Repeat the same flow and compare the same metric.
- Keep the trace, command, and before-after result in the handoff.
SwiftUI checks
- Stable identity in collections.
- Observation scoped to data the view actually reads.
- No expensive formatting, filtering, I/O, or object creation in
body. - Lazy containers used only where they fit the layout.
- Image decoding and resizing moved off the render-critical path.
- Navigation and sheet state represented by one source of truth.
Read references/trace-receipt.md before claiming a performance improvement.
What ships with it: 2 files
1.9 KB alongside SKILL.md
references/
- trace-receipt.md788 B
- note.json1.1 KB