swift-architecture-skill

To choose the right Swift architecture for an iOS feature, analyze the task context to recommend the best pattern, such as MVVM, MVI, TCA, or VIPER, by running fit checks and comparing alternatives to ensure maintainability and clean separation of concerns.

The best way to structure an async strategy and module layout in SwiftUI is to generate deliverables based on the selected architecture pattern, which defines state boundaries, module organization, and UI-specific guidance for maintainable code.

Yes, you can use this architecture selection process for watchOS apps and pull request reviews, as it analyzes task context for both platforms and appends a tailored checklist to validate PR compliance with the chosen architecture pattern.

To migrate an existing iOS codebase to a different architecture pattern like TCA or Clean Swift, generate a migration path that outlines the transition steps from your current pattern while maintaining state boundaries and testing plans throughout the refactor.

When refactoring an iOS app for testability, the patterns evaluated include MVVM, MVI, TCA, Clean, VIPER, Reactive, MVP, and Coordinator, each assessed through fit checks to determine the optimal choice for your specific feature requirements.

Your iOS codebase has maintainability issues after choosing an architecture pattern likely due to inconsistent application of the pattern's state boundaries and async strategy, which can be resolved by validating compliance using a tailored PR review checklist.