Swiftui View Refactor

**Judgement:** This skill is a focused, opinionated refactoring assistant for SwiftUI views, well-suited to enforcing consistent structure, MV-style patterns, and modern Observation usage in existing code. **Strengths & benefits:** - Produces a predictable file layout (env → properties → init → body → helpers), improving readability and team consistency. - Encourages small, composable views and clear separation between view state and business logic. - Normalizes view model handling around non-optional @State initialization and dependency injection through the view’s init. - Promotes correct usage of the Observation framework for @Observable models. **Key risks / limitations:** - Opinionated toward modern SwiftUI/Observation patterns; may not align with projects targeting older OSes or using legacy patterns (e.g., @StateObject/@ObservedObject + Combine) as primary architecture. - Structural refactors of large views can be intrusive, so diffs may be sizable and require careful review to ensure no subtle behavior changes. - If the existing architecture intentionally uses heavier view models or different layering, the MV-first bias may conflict with project conventions. **Recommended scenarios:** - Use when you explicitly want to clean up, reorder, or standardize SwiftUI view files, especially those that have grown large or inconsistent. - Use when migrating a codebase toward modern Observation-based patterns and clearer dependency injection in views. - Avoid or use cautiously in legacy SwiftUI projects with strict architectural constraints or non-Observation-based patterns unless you plan to modernize those areas.