Swiftui Performance Audit

**Judgement:** Strong, focused skill for SwiftUI runtime performance analysis and remediation. Well worth enabling for any environment that supports iOS/macOS SwiftUI projects. **What it does well** - Provides a structured, repeatable process: start with code review, escalate to Instruments only when needed. - Targets the real SwiftUI pain points: state-driven invalidation storms, unstable list identity, heavy work in `body`, layout complexity, image decoding, and over-animated view trees. - Offers concrete, code-level guidance (e.g., precomputing filtered/sorted collections, caching formatters, stabilizing `ForEach` IDs, narrowing observable state scope). - Promotes evidence-based tuning by asking for baseline vs. post-fix metrics and specific traces/screenshots. **Risks & Limitations** - Highly domain-specific: only useful for SwiftUI apps; not applicable to UIKit, Android, web, or backend performance issues. - Still depends on the user’s ability to provide representative code and, when requested, proper Instruments captures; weak input will limit diagnostic accuracy. - May over-rely on heuristic patterns when Instruments data is not available, so conclusions should be treated as educated guidance rather than definitive profiling results. **Recommended scenarios** - SwiftUI apps with stuttery scrolling in `List`/`ScrollView`, slow navigation transitions, or visibly janky animations. - Situations where CPU spikes, frame drops, or memory pressure are suspected to be tied to view recomposition or layout, but the root cause is unclear. - Code reviews aimed at proactively hardening performance in complex SwiftUI screens before release. - Teaching or mentoring developers on common SwiftUI performance anti-patterns and how to profile them with Instruments.