swiftui-expert-skill

Yes, SwiftUI accessibility considerations enforce up-to-date API usage and proper availability gating during feature implementation. Applying these guidelines during refactoring tasks ensures that macOS-specific APIs and iOS 26+ Liquid Glass patterns are correctly adopted across the project lifecycle.

The best way to manage SwiftUI state involves using @State for private internal state, @StateObject for lifecycle-managed objects, and @Observable for data-flow clarity. Proper application of these property wrappers ensures maintainable code and enforces Apple-recommended practices for data-flow consistency.

Yes, this approach supports macOS-specific APIs and iOS 26+ Liquid Glass patterns by enforcing availability handling for feature gating. It provides decision trees and guidelines to adopt platform-specific patterns correctly, ensuring proper macOS integration and modern iOS feature implementation.

Improve SwiftUI performance by extracting complex views, using stable ForEach identities, and implementing lazy containers. These view structure guidelines enhance diffing and rendering efficiency, directly addressing performance issues caused by complex view hierarchies and unstable identifiers.

Yes, you can use these guidelines to refactor existing SwiftUI projects by generating a corrective implementation plan. The review process identifies deviations from best-practice patterns and applies Apple-recommended guidelines to improve state management, view composition, and accessibility.