swift-perf-audit

A SwiftUI performance audit identifies main-thread blocking by orchestrating parallel multi-agent codebase scans across SwiftUI views and terminal integration. It classifies severity and proposes concrete, minimal-change fixes to eliminate sluggish transitions without refactoring.

Excessive view invalidation storms in SwiftUI apps are caused by inefficient state management and reactive patterns triggering unnecessary re-renders. A full-stack audit scans the codebase to surface these issues, quantifies their impact on chat streaming, and guides targeted fixes.

Auditing SwiftUI animation overhead in a macOS terminal app requires a phased symptom collection process followed by parallel codebase analysis. The audit traces animation overhead and async anti-patterns to propose minimal invasive changes that respect libghostty integration constraints.

No, the performance audit explicitly avoids invasive refactoring for SwiftUI bottlenecks. It enforces guardrails to preserve architecture constraints by generating concrete, minimal-change fixes that safely resolve main-thread blocking and view invalidation storms.

The best way to quantify SwiftUI performance bottlenecks is through a three-agent codebase scan that classifies issues by severity. This multi-agent approach analyzes main-thread blocking, re-renders, and async anti-patterns to produce prioritized optimization steps.

Yes, you can use this audit to fix choppy chat streaming in a macOS app. It specifically targets the SwiftUI and terminal integration layers, identifying async anti-patterns and main-thread blocking to guide minimal changes that restore smooth streaming performance.