What problem does it solve? SwiftUI developers often struggle with choosing the right state ownership model, wiring navigation across tabs, and avoiding anti-patterns like giant views or scattered sheet logic. This Skill provides concrete, battle-tested patterns for structuring SwiftUI UI code so screens stay composable, performant, and consistent with modern APIs. ## Core Features & Use Cases - State ownership guidance: Decision table mapping scenarios to @State, @Binding, @Observable, @Environment, or legacy @StateObject/@ObservedObject for iOS 16 and earlier. - Navigation and presentation patterns: Per-tab NavigationStack routing with enum-based routes, centralized enum-driven sheets, and deep link handling through a single router. - Component reference library: Over 20 focused references covering TabView, List, Form, grids, scroll-reveal surfaces, haptics, theming, previews, async task lifecycle, and performance guardrails. - Use Case: When building a new settings screen, follow the Form reference for grouped sections, apply the theming pattern for consistent colors, and wire presentation through the centralized sheet enum instead of ad-hoc boolean flags. ## Quick Start Ask the assistant to design or refactor a SwiftUI screen, for example: build a tab-based app shell with per-tab navigation stacks and enum-driven sheets following the SwiftUI UI patterns.