swiftui-expert-skill

Use @State for simple value-type UI state owned by the current view, while @StateObject initializes external reference-type models. For modern SwiftUI state management, this Skill recommends adopting the @Observable macro over @StateObject to ensure optimal performance and proper view lifecycle bindings.

Optimize SwiftUI performance by reducing unnecessary view body recalculations, enforcing proper state management boundaries, and adopting modern APIs. This Skill audits view composition to identify expensive redraws and suggests refactoring code to isolate state dependencies and leverage SwiftUI's built-in diffing efficiently.

SwiftUI code review best practices involve checking for proper state management, modular view composition, and modern API adoption. This Skill enforces guidelines by auditing existing code to ensure maintainable view hierarchies, correct Swift concurrency usage, and adherence to the latest Apple development recommendations.

Yes, this SwiftUI guidance covers modern iOS features like Liquid Glass. It enforces best practices for modern API adoption, ensuring your iOS development codebase integrates the latest Apple interface guidelines and Swift concurrency patterns correctly for optimal performance and maintainability.

Refactor legacy SwiftUI code to use Swift concurrency by migrating to modern property wrappers like @Observable and adopting structured concurrency patterns. This Skill provides expert guidance on updating state management and view composition to align with current Apple frameworks and eliminate outdated async patterns.

A limitation of @Observable in SwiftUI state management is its requirement for iOS 17 or later, making it unsuitable for older deployment targets. When targeting older iOS versions, this Skill guides you to fall back to @StateObject or @ObservedObject to maintain compatibility without breaking performance.