What problem does it solve? SwiftUI developers often struggle with choosing the right architecture pattern, managing state correctly across view hierarchies, and avoiding performance pitfalls like unstable view identity and unnecessary re-renders. This Skill provides expert guidance grounded in Apple's own recommendations to build maintainable, performant SwiftUI applications. ## Core Features & Use Cases - Architecture Pattern Guidance: Compares MV, MVVM, Clean Architecture, and modular approaches with concrete Swift code examples and decision criteria for app size and team structure. - State Management Reference: Explains when to use @State, @Binding, @StateObject, @ObservedObject, @EnvironmentObject, and the modern @Observable macro, with a source-of-truth hierarchy model. - Performance & Identity Best Practices: Covers stable identifiers in ForEach, inert modifiers, dependency scope minimization, and common anti-patterns to avoid. - Use Case: When building a client/server iOS app, ask how to structure stores and views; the Skill recommends a single @Observable store per bounded context with container/presenter view separation, plus testable form structs and protocol-based network mocking. ## Quick Start Ask how to structure state management and navigation for a new SwiftUI app with multiple screens and a shared data store.
