swift-architecture-skill

Swift architecture pattern selection involves evaluating feature complexity against references for MVVM, VIPER, MVI, and TCA. This provides concrete boundary definitions and assembly patterns to ensure consistent, testable module wiring across SwiftUI and UIKit.

MVVM and TCA differ in state management boundaries and boilerplate. The Skill provides references detailing when to apply each pattern, offering distinct boundary definitions and assembly guidance to promote consistent tooling and scalable feature development in SwiftUI.

VIPER architecture supports both UIKit and SwiftUI. Concrete assembly and wiring patterns are provided for both UI frameworks, ensuring clear dependency rules, testable patterns, and strict module boundaries regardless of the presentation layer.

Wiring a module using Clean Architecture involves applying provided assembly patterns to define dependencies and boundaries. This reduces guesswork by offering concrete structure, testing strategies, and clear guidance for safe, scalable feature development.

MVI may be unsuitable when feature complexity does not justify its state management overhead. Architecture references provide guidance on when to apply MVI versus lighter alternatives, ensuring you avoid unnecessary boilerplate while maintaining testable boundaries.