What problem does it solve?
This Skill eliminates the risk of selecting the wrong iOS/macOS app architecture, which leads to unmaintainable Massive View Controllers, wasted development time, and expensive late-stage rewrites. It provides a decision compass tailored to the Swift 6 / iOS 26 era, ensuring your architecture matches your project's actual size, team structure, and domain complexity rather than over-engineered "future-proof" choices.
Core Features & Use Cases
- Decision Compass: A guided questionnaire and matrix to recommend the optimal architecture stack (MVC, MVVM + Coordinator/Router, Clean Architecture, VIPER, MVI, TCA) based on team size, project lifetime, domain complexity, UI framework, and testing requirements.
- Implementation Guidance: Detailed reference files for each supported stack, covering ViewModel design, navigation patterns, dependency injection, SPM modularization, Swift Concurrency placement, and cross-cutting error/networking/persistence layers.
- Migration & Anti-Pattern Avoidance: Additive migration paths between patterns (e.g. MVC → MVVM, MVVM → Clean) and a list of universal anti-patterns to avoid, such as mixing architecture patterns per feature or over-engineering small projects.
- Use Case Example: A solo developer starting a 3-screen CRUD app gets a recommendation for MVC with manual DI, while a 4-person team building a 2-year fintech app with rich business rules is guided to Clean Architecture with SPM modularization.
Quick Start
Ask the ios-app-architecture skill to recommend the optimal architecture stack for your new iOS project, providing answers to the 5 intake questions about team size, project lifetime, domain complexity, UI framework, and testing requirements.