Will it force a View Model on my simple views?

No, it follows an MV-first approach and only refactors View Models if they already exist or if the request specifically calls for one.

Does this skill change my application's business logic?

No, the skill is designed to keep behavior intact while improving code structure, ordering, and architectural patterns.

How does it handle extremely large SwiftUI files?

For files exceeding 300 lines, it uses Swift extensions and // MARK: comments to group related helpers, actions, and subviews for better navigation.

Can it split views into separate files?

It focuses on extracting complex components into dedicated View types within the same file or new structs to improve composability.

Does it support the modern Swift Observation framework?

Yes, it specifically optimizes for @Observable usage, ensuring reference types are stored as @State in root views and passed explicitly.

SwiftUI View Architect

Name: SwiftUI View Architect
Author: robinsalehjan

byrobinsalehjan

0•

Mobile Development

Refactors SwiftUI views to ensure consistent structure, clean dependency injection, and optimized Observation usage.

This skill streamlines SwiftUI development by applying professional structural standards to view files, transforming cluttered UI code into maintainable, production-ready components. It automatically reorders view properties (from Environment to Helpers), enforces Model-View patterns, and ensures safe View Model initialization using modern @Observable macros. By intelligently splitting large view bodies into composable subviews and managing dependency injection through view initializers, it improves code readability and architectural integrity without altering your existing business logic.

Características Principales

01Non-optional View Model initialization and safe dependency injection

02Code organization via MARK extensions for files exceeding 300 lines

03Standardized property ordering (Environment, State, Init, Body, Helpers)

04Automatic decomposition of large view bodies into manageable subviews

050 GitHub stars

06Optimized @Observable state management implementation

Casos de Uso

01Migrating legacy SwiftUI state management to the modern Observation framework

02Cleaning up monolithic SwiftUI files with massive, unreadable body blocks

03Standardizing dependency injection patterns across a professional iOS project

Características Principales

01Non-optional View Model initialization and safe dependency injection

02Code organization via MARK extensions for files exceeding 300 lines

03Standardized property ordering (Environment, State, Init, Body, Helpers)

04Automatic decomposition of large view bodies into manageable subviews

050 GitHub stars

06Optimized @Observable state management implementation

Casos de Uso

01Migrating legacy SwiftUI state management to the modern Observation framework

02Cleaning up monolithic SwiftUI files with massive, unreadable body blocks

03Standardizing dependency injection patterns across a professional iOS project