swiftui-view-refactor · harperreed — Claude Code skill for SwiftUI refactoring

What swiftui-view-refactor does

The skill defines a consistent order for SwiftUI view declarations: environment values and stored properties first, followed by computed non-view values, initialization, body, and supporting view builders or functions. Large screen bodies should be divided into smaller components, with each receiving only the data, bindings, and callbacks it needs. The goal is to keep view code readable without adding unnecessary architectural layers.

Its default direction is Model-View. Business rules belong in models and services, while views coordinate state with @State, @Environment, @Query, task, and onChange. Root views should hold @Observable reference objects in @State. When a view already has a view model, initialize it with dependencies passed through init and avoid optional storage where the design allows it.

Files longer than roughly 300 lines can be organized with private extensions and purpose-specific // MARK: - sections. The refactor should preserve existing behavior unless the request calls for a functional change. This matters when extracting subviews: changing the structure should not silently alter the screen's layout or business rules.