swift-ui

This skill provides expert-level guidance for building scalable and polished native applications using SwiftUI. It emphasizes modern implementation patterns, moving away from complex ViewModel-heavy architectures toward streamlined, state-driven designs. Designed for iOS and macOS developers, the skill covers the entire view lifecycle, from structural composition to reactive data management via SwiftData. It serves as an authoritative reference for implementing system-native interfaces while adhering to Apple's Human Interface Guidelines.

• Advanced View Composition: Techniques for building modular UI components using ViewBuilder, custom modifiers, and generics to ensure maintainable codebases.

• Reactive State Management: Deep dive into property wrappers like @State, @Binding, @StateObject, and Environment values to manage data flow effectively without unnecessary overhead.

• Data Persistence: Direct integration patterns for SwiftData, including the @Model macro, @Query fetching, and ModelContainer orchestration for reactive, persistent storage.

• Adaptive Layout Engineering: Implementation of responsive layouts utilizing stacks, LazyGrids, and GeometryReader to handle diverse screen sizes and device constraints.

• Accessibility and Inclusivity: Comprehensive support for VoiceOver, Dynamic Type, and accessibility traits to ensure inclusive user experiences.

• Motion and Animation: Best practices for implementing implicit and explicit animations, spring transitions, and gesture-driven interactivity.

• Use this skill when architecting new features or refactoring legacy view structures to improve readability and performance.

• Ideal for debugging complex state sync issues or implementing data-driven views that require real-time updates from SwiftData.

• Developers should provide context regarding the specific UI component or data flow pattern they are implementing to receive the most accurate architectural advice.

• Constraints: Focuses on native SwiftUI and SwiftData; does not cover UIKit/AppKit legacy transitions or external third-party database frameworks. It encourages a declarative approach, rejecting monolithic ViewModel patterns in favor of environment-based dependency injection and focused state handling.