swiftui-ui-patterns

Best practices and patterns for building SwiftUI views, navigation, and state management. Choose a track based on your goal: Use the narrowest state tool that matches the ownership model: Choose the ownership location first, then pick the wrapper. Do not introduce a reference model when plain value state is enough. Use references/components-index.md as the entry point. Each component reference should include: - Covers state ownership strategies (from @State and @Binding to @Observable on iOS 17+), async/await patterns with .task , and environment injection for shared dependencies - Includes cross-cutting references for NavigationStack routing, sheet presentation, deep linking, and app-level wiring with concrete ownership rules - Provides component-specific guidance via indexed references, with anti-patterns and performance considerations for large or scroll-heavy screens - Workflow-driven approach: define state ownership and dependencies first, sketch hierarchy, implement async loading with explicit states, then validate with previews and builds - Identify the feature or screen and the primary interaction model (list, detail, editor, settings, tabbed). - Find a nearby example in the repo with rg "TabView\(" or similar, then read the closest SwiftUI view. - Apply local conventions: prefer SwiftUI-native state, keep state local when possible, and use environment injection for...