neo-swift-uilisted

# Modern SwiftUI (iOS 16+) Expert Skill ## Trigger On - The user asks to write, debug, refactor, or review SwiftUI code. - The target project version is iOS 16 or higher (utilizing features like `NavigationStack`, `Grid`, etc.). - Development involves state management (`@State`, `@Observable`), custom layouts, or animations. ## Workflow 1. **Perceive (Version and Environment Awareness):** - Confirm if the deployment target is iOS 16+. - Identify the current state management paradigm (traditional `ObservableObject` vs. modern `@Observable`). - Assess the usage of navigation components (check if deprecated `NavigationView` is still in use). 2. **Reason (Planning Phase):** - Plan the view hierarchy to maximize reusability and minimize redundant `body` computations. - Enforce the use of `NavigationStack` or `NavigationSplitView` for navigation needs. - Select the correct data flow tools based on data lifecycle (`State`, `Binding`, `Environment`). 3. **Act (Execution Phase):** - Follow SwiftUI core principles to write concise, declarative Swift code. - Use `Grid`, `ViewThatFits`, or custom `Layout` protocols to implement complex layouts. - Leverage modern modifiers (e.g., `.sheet` with `detents`). 4. **Validate (Standard Validation):** - Check for "God Views" (views with excessive logic or `body` content) and suggest splitting them. - Ensure `@State` and `@Binding` are used correctly to avoid unnecessary view refreshes. - Verify that the UI re