What problem does it solve? macOS SwiftUI codebases often grow into monolithic files where one root view owns window scaffolding, settings, toolbars, commands, and detail layout, making the app hard to maintain and extend. This Skill provides a structured refactoring methodology to split oversized views, stabilize scene and selection structure, and keep AppKit interop contained. ## Core Features & Use Cases - Scene and File Decomposition: Split apps into explicit scene roots and organized directories (App/, Views/, Models/, Stores/, Services/, Support/) with a predictable file ordering. - Subview Extraction: Replace large computed view fragments with dedicated subview types that receive explicit data, bindings, and actions. - State and Interop Discipline: Apply correct usage of @SceneStorage, @AppStorage, @Observable/@State, and isolate AppKit bridges behind narrow wrappers. - Use Case: Given a single 800-line Swift file containing the @main app, sidebar, detail view, models, and a URLSession client, refactor it into a minimal app entrypoint, focused feature views, extracted models and stores, and a Services/ networking client while preserving behavior. ## Quick Start Use the view-refactor skill to split my oversized macOS SwiftUI ContentView into focused subviews and move the networking code into a Services directory.