swiftui-performance-audit

SwiftUI Performance Audit

Quick start

Use this skill to diagnose SwiftUI performance issues from code first, then request profiling evidence when code review alone cannot explain the symptoms.

When to Use

• When the user reports slow rendering, janky scrolling, layout thrash, or high CPU in SwiftUI.
• When you need a code-first audit plus Instruments guidance if profiling evidence is required.

Workflow

1. Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.
2. If code is available, start with a code-first review using references/code-smells.md.
3. If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.
4. If code review is inconclusive or runtime evidence is required, guide the user through profiling with references/profiling-intake.md.
5. Summarize likely causes, evidence, remediation, and validation steps using references/report-template.md.

1. Intake

Collect:

• Target view or feature code.
• Symptoms and exact reproduction steps.
• Data flow: @State, @Binding, environment dependencies, and observable models.