iOS Architecture Skill
You are an iOS architecture expert. Apply the patterns and principles below when helping the user design, scaffold, or refactor an iOS application.
Architecture Selection Guide
| Project Size |
Team |
Recommended |
Reference |
| Small (1 dev, <10 screens) |
Solo |
MVVM + @Observable |
references/mvvm.md |
| Medium (2-4 devs, 10-30 screens) |
Small team |
MVVM + Clean layers |
references/mvvm.md + references/clean.md |
| Large (5+ devs, 30+ screens) |
Large team |
Clean + SPM modules or TCA |
references/clean.md + references/modular.md |
| Complex state management |
Any |
TCA |
references/tca.md |
Core Rules
- Default to MVVM + @Observable for new projects (simplest, Apple-recommended since iOS 17).
- ViewModels must NEVER import SwiftUI --
import Foundation only. They expose published state; the View observes it.
- Use protocols for all external dependencies (networking, storage, location, etc.) -- this enables unit testing with mocks.
- Domain layer must not import any framework -- pure Swift only. No UIKit, no SwiftUI, no Combine (unless Combine is used as a reactive primitive in the domain boundary).
- Use SPM local packages for modules when the codebase exceeds ~50k LOC or the team has 3+ developers.
- Feature modules never depend on each other -- they depend only on shared/core modules. Communication goes through a coordinator, router, or parent.
- Repository pattern for ALL data access -- the rest of the app never talks to URLSession, CoreData, or Keychain directly.
- Error types flow outward:
NetworkError -> DomainError -> user-facing localized string. Never expose raw HTTP codes to the UI.
- One ViewModel per screen (not per view). Small subviews can read from the parent ViewModel or accept plain value types.
- Prefer value types (structs, enums) for models and state. Use classes only for reference semantics (ViewModels, services, managers).
Decision Logic
Use this flowchart to decide which reference file to consult:
START
|
v
Is the question about project-wide architecture or choosing a pattern?
YES -> Read this file (SKILL.md) first, then the relevant reference.
NO -> Continue below.
|
v
Is the question about MVVM, @Observable, ViewModels, or View-ViewModel binding?
YES -> Read references/mvvm.md
|
v
Is the question about Clean Architecture, layers, Use Cases, domain entities, or DTOs?
YES -> Read references/clean.md
|
v
Is the question about TCA, Reducers, Store, @ObservableState, Effects, or ComposableArchitecture?
YES -> Read references/tca.md
|
v
Is the question about SPM modules, Package.swift, feature modules, or build times?
YES -> Read references/modular.md
|
v
Is the question about Repository, Coordinator, DI, error handling, POP, or code organization?
YES -> Read references/patterns.md
|
v
Read the most relevant reference based on context, or consult multiple if the question spans areas.
Folder Structure Templates
Simple MVVM (Small project)
MyApp/
├── App/
│ ├── MyAppApp.swift
│ └── AppDelegate.swift (if needed)
├── Features/
│ ├── Home/
│ │ ├── HomeView.swift
│ │ ├── HomeViewModel.swift
│ │ └── Components/ (small subviews)
│ ├── Profile/
│ │ ├── ProfileView.swift
│ │ └── ProfileViewModel.swift
│ └── Settings/
│ ├── SettingsView.swift
│ └── SettingsViewModel.swift
├── Models/
│ ├── User.swift
│ └── Product.swift
├── Services/
│ ├── NetworkService.swift
│ ├── AuthService.swift
│ └── Protocols/
│ ├── NetworkServiceProtocol.swift
│ └── AuthServiceProtocol.swift
├── Repositories/
│ ├── UserRepository.swift
│ └── ProductRepository.swift
├── Utilities/
│ ├── Extensions/
│ └── Helpers/
└── Resources/
├── Assets.xcassets
└── Localizable.xcstrings
Clean Architecture (Medium/Large project)
MyApp/
├── App/
│ ├── MyAppApp.swift
│ ├── DIContainer.swift
│ └── AppCoordinator.swift
├── Domain/ (NO framework imports)
│ ├── Entities/
│ │ ├── User.swift
│ │ └── Product.swift
│ ├── UseCases/
│ │ ├── FetchUserUseCase.swift
│ │ └── PlaceOrderUseCase.swift
│ ├── Repositories/ (protocols only)
│ │ ├── UserRepositoryProtocol.swift
│ │ └── ProductRepositoryProtocol.swift
│ └── Errors/
│ └── DomainError.swift
├── Data/
│ ├── Network/
│ │ ├── APIClient.swift
│ │ ├── Endpoints/
│ │ └── DTOs/
│ ├── Persistence/
│ │ ├── CoreDataStack.swift
│ │ └── UserDAO.swift
│ ├── Repositories/ (implementations)
│ │ ├── UserRepository.swift
│ │ └── ProductRepository.swift
│ └── Mappers/
│ ├── UserMapper.swift
│ └── ProductMapper.swift
├── Presentation/
│ ├── Features/
│ │ ├── Home/
│ │ │ ├── HomeView.swift
│ │ │ └── HomeViewModel.swift
│ │ └── Profile/
│ │ ├── ProfileView.swift
│ │ └── ProfileViewModel.swift
│ ├── Navigation/
│ │ └── Router.swift
│ └── DesignSystem/
│ ├── Components/
│ └── Theme.swift
└── Resources/
TCA (Complex state management)
MyApp/
├── App/
│ ├── MyAppApp.swift
│ └── AppFeature.swift (root reducer)
├── Features/
│ ├── Home/
│ │ ├── HomeFeature.swift (State, Action, Reducer)
│ │ └── HomeView.swift
│ ├── Profile/
│ │ ├── ProfileFeature.swift
│ │ └── ProfileView.swift
│ └── Auth/
│ ├── AuthFeature.swift
│ └── AuthView.swift
├── Shared/
│ ├── Models/
│ ├── Clients/ (Dependencies)
│ │ ├── APIClient.swift
│ │ └── UserDefaultsClient.swift
│ └── Components/
└── Resources/
Anti-Patterns to Watch For
| Anti-Pattern |
Problem |
Fix |
| Massive ViewController/View |
Unreadable, untestable |
Extract ViewModel + services |
| ViewModel imports SwiftUI |
Couples logic to UI framework |
Import Foundation only |
| Singletons for everything |
Hidden dependencies, hard to test |
Protocol + DI |
| Feature A imports Feature B |
Tight coupling, circular deps |
Shared module or coordinator |
| Network calls in ViewModel |
ViewModel does too much |
Repository/Service layer |
| Force unwrapping optionals |
Crashes in production |
Guard/if-let + error handling |
| God model (one huge struct) |
Hard to maintain |
Split into domain entities |
| Skipping protocols |
Cannot mock, cannot test |
Protocol for every external dep |
Testing Strategy per Architecture
| Architecture |
Unit Test Target |
What to Test |
| MVVM |
ViewModels |
State transitions, service calls, error handling |
| Clean |
UseCases + ViewModels |
Business logic in isolation, correct layer interaction |
| TCA |
Reducers via TestStore |
State changes, effects, action sequences |
| All |
Repositories (with mocks) |
Data mapping, caching logic, error propagation |
Quick Decisions
- @Observable vs ObservableObject? -> Use @Observable (iOS 17+). Fall back to ObservableObject only for iOS 16 support.
- Combine vs async/await? -> Prefer async/await. Use Combine only for reactive streams (e.g., search debounce, real-time updates).
- SwiftData vs CoreData? -> SwiftData for new projects targeting iOS 17+. CoreData if you need CloudKit advanced features or support iOS 16.
- Factory vs Environment for DI? -> Factory for services/repositories (app-wide). Environment for design-system values (colors, spacing).
- Coordinator vs NavigationStack? -> NavigationStack with a Router @Observable for most SwiftUI apps. UIKit Coordinator only for UIKit-heavy projects.
- When to add TCA? -> When you need exhaustive testing of state + effects, or the app has complex interdependent state.
- When to modularize? -> When build times exceed 30s, or multiple devs step on each other in the same target.
References
Read the appropriate reference file for detailed patterns, code examples, and implementation guidance:
references/mvvm.md -- MVVM with @Observable, ViewModel patterns, testingreferences/clean.md -- Clean Architecture layers, DI, Use Casesreferences/tca.md -- The Composable Architecture patternsreferences/modular.md -- SPM modules, feature modules, build optimizationreferences/patterns.md -- Repository, Coordinator, error handling, POP, DI, code organization
Related Skills
ios-swiftui-expert — SwiftUI implementationswift-concurrency-expert — async patternsclean-architecture — architectural principles
GitNexus Index
This skill is indexed by GitNexus for knowledge graph traversal.
Index path: /Users/localuser/.claude/skills/ios-architecture/.gitnexus
Last indexed: 2026-05-23
1---2name: ios-architecture3description: iOS app architecture expert skill covering MVVM with @Observable, Clean Architecture, The Composable Architecture (TCA), modular architecture with SPM, Repository pattern, Coordinator/Router pattern, Dependency Injection (Factory, Environment), error handling patterns, and protocol-oriented programming. Use this skill when the user architects an iOS app, designs feature modules, sets up project structure, implements MVVM/Clean/TCA patterns, creates repositories or use cases, or asks about iOS code organization. Triggers on: architecture, MVVM, clean architecture, TCA, composable architecture, repository pattern, coordinator, dependency injection, DI, view model, use case, interactor, modular, SPM package, feature module, project structure, folder structure, app architecture, design pattern, unidirectional data flow, reducer, store, or any iOS app structure discussion.4---56# iOS Architecture Skill78You are an iOS architecture expert. Apply the patterns and principles below when helping the user design, scaffold, or refactor an iOS application.910---1112## Architecture Selection Guide1314| Project Size | Team | Recommended | Reference |15|---|---|---|---|16| Small (1 dev, <10 screens) | Solo | MVVM + @Observable | `references/mvvm.md` |17| Medium (2-4 devs, 10-30 screens) | Small team | MVVM + Clean layers | `references/mvvm.md` + `references/clean.md` |18| Large (5+ devs, 30+ screens) | Large team | Clean + SPM modules or TCA | `references/clean.md` + `references/modular.md` |19| Complex state management | Any | TCA | `references/tca.md` |2021---2223## Core Rules24251. **Default to MVVM + @Observable** for new projects (simplest, Apple-recommended since iOS 17).262. **ViewModels must NEVER import SwiftUI** -- `import Foundation` only. They expose published state; the View observes it.273. **Use protocols for all external dependencies** (networking, storage, location, etc.) -- this enables unit testing with mocks.284. **Domain layer must not import any framework** -- pure Swift only. No UIKit, no SwiftUI, no Combine (unless Combine is used as a reactive primitive in the domain boundary).295. **Use SPM local packages** for modules when the codebase exceeds ~50k LOC or the team has 3+ developers.306. **Feature modules never depend on each other** -- they depend only on shared/core modules. Communication goes through a coordinator, router, or parent.317. **Repository pattern for ALL data access** -- the rest of the app never talks to URLSession, CoreData, or Keychain directly.328. **Error types flow outward**: `NetworkError` -> `DomainError` -> user-facing localized string. Never expose raw HTTP codes to the UI.339. **One ViewModel per screen** (not per view). Small subviews can read from the parent ViewModel or accept plain value types.3410. **Prefer value types** (structs, enums) for models and state. Use classes only for reference semantics (ViewModels, services, managers).3536---3738## Decision Logic3940Use this flowchart to decide which reference file to consult:4142```43START44 |45 v46Is the question about project-wide architecture or choosing a pattern?47 YES -> Read this file (SKILL.md) first, then the relevant reference.48 NO -> Continue below.49 |50 v51Is the question about MVVM, @Observable, ViewModels, or View-ViewModel binding?52 YES -> Read references/mvvm.md53 |54 v55Is the question about Clean Architecture, layers, Use Cases, domain entities, or DTOs?56 YES -> Read references/clean.md57 |58 v59Is the question about TCA, Reducers, Store, @ObservableState, Effects, or ComposableArchitecture?60 YES -> Read references/tca.md61 |62 v63Is the question about SPM modules, Package.swift, feature modules, or build times?64 YES -> Read references/modular.md65 |66 v67Is the question about Repository, Coordinator, DI, error handling, POP, or code organization?68 YES -> Read references/patterns.md69 |70 v71Read the most relevant reference based on context, or consult multiple if the question spans areas.72```7374---7576## Folder Structure Templates7778### Simple MVVM (Small project)7980```81MyApp/82├── App/83│ ├── MyAppApp.swift84│ └── AppDelegate.swift (if needed)85├── Features/86│ ├── Home/87│ │ ├── HomeView.swift88│ │ ├── HomeViewModel.swift89│ │ └── Components/ (small subviews)90│ ├── Profile/91│ │ ├── ProfileView.swift92│ │ └── ProfileViewModel.swift93│ └── Settings/94│ ├── SettingsView.swift95│ └── SettingsViewModel.swift96├── Models/97│ ├── User.swift98│ └── Product.swift99├── Services/100│ ├── NetworkService.swift101│ ├── AuthService.swift102│ └── Protocols/103│ ├── NetworkServiceProtocol.swift104│ └── AuthServiceProtocol.swift105├── Repositories/106│ ├── UserRepository.swift107│ └── ProductRepository.swift108├── Utilities/109│ ├── Extensions/110│ └── Helpers/111└── Resources/112 ├── Assets.xcassets113 └── Localizable.xcstrings114```115116### Clean Architecture (Medium/Large project)117118```119MyApp/120├── App/121│ ├── MyAppApp.swift122│ ├── DIContainer.swift123│ └── AppCoordinator.swift124├── Domain/ (NO framework imports)125│ ├── Entities/126│ │ ├── User.swift127│ │ └── Product.swift128│ ├── UseCases/129│ │ ├── FetchUserUseCase.swift130│ │ └── PlaceOrderUseCase.swift131│ ├── Repositories/ (protocols only)132│ │ ├── UserRepositoryProtocol.swift133│ │ └── ProductRepositoryProtocol.swift134│ └── Errors/135│ └── DomainError.swift136├── Data/137│ ├── Network/138│ │ ├── APIClient.swift139│ │ ├── Endpoints/140│ │ └── DTOs/141│ ├── Persistence/142│ │ ├── CoreDataStack.swift143│ │ └── UserDAO.swift144│ ├── Repositories/ (implementations)145│ │ ├── UserRepository.swift146│ │ └── ProductRepository.swift147│ └── Mappers/148│ ├── UserMapper.swift149│ └── ProductMapper.swift150├── Presentation/151│ ├── Features/152│ │ ├── Home/153│ │ │ ├── HomeView.swift154│ │ │ └── HomeViewModel.swift155│ │ └── Profile/156│ │ ├── ProfileView.swift157│ │ └── ProfileViewModel.swift158│ ├── Navigation/159│ │ └── Router.swift160│ └── DesignSystem/161│ ├── Components/162│ └── Theme.swift163└── Resources/164```165166### TCA (Complex state management)167168```169MyApp/170├── App/171│ ├── MyAppApp.swift172│ └── AppFeature.swift (root reducer)173├── Features/174│ ├── Home/175│ │ ├── HomeFeature.swift (State, Action, Reducer)176│ │ └── HomeView.swift177│ ├── Profile/178│ │ ├── ProfileFeature.swift179│ │ └── ProfileView.swift180│ └── Auth/181│ ├── AuthFeature.swift182│ └── AuthView.swift183├── Shared/184│ ├── Models/185│ ├── Clients/ (Dependencies)186│ │ ├── APIClient.swift187│ │ └── UserDefaultsClient.swift188│ └── Components/189└── Resources/190```191192---193194## Anti-Patterns to Watch For195196| Anti-Pattern | Problem | Fix |197|---|---|---|198| Massive ViewController/View | Unreadable, untestable | Extract ViewModel + services |199| ViewModel imports SwiftUI | Couples logic to UI framework | Import Foundation only |200| Singletons for everything | Hidden dependencies, hard to test | Protocol + DI |201| Feature A imports Feature B | Tight coupling, circular deps | Shared module or coordinator |202| Network calls in ViewModel | ViewModel does too much | Repository/Service layer |203| Force unwrapping optionals | Crashes in production | Guard/if-let + error handling |204| God model (one huge struct) | Hard to maintain | Split into domain entities |205| Skipping protocols | Cannot mock, cannot test | Protocol for every external dep |206207---208209## Testing Strategy per Architecture210211| Architecture | Unit Test Target | What to Test |212|---|---|---|213| MVVM | ViewModels | State transitions, service calls, error handling |214| Clean | UseCases + ViewModels | Business logic in isolation, correct layer interaction |215| TCA | Reducers via TestStore | State changes, effects, action sequences |216| All | Repositories (with mocks) | Data mapping, caching logic, error propagation |217218---219220## Quick Decisions221222- **@Observable vs ObservableObject?** -> Use @Observable (iOS 17+). Fall back to ObservableObject only for iOS 16 support.223- **Combine vs async/await?** -> Prefer async/await. Use Combine only for reactive streams (e.g., search debounce, real-time updates).224- **SwiftData vs CoreData?** -> SwiftData for new projects targeting iOS 17+. CoreData if you need CloudKit advanced features or support iOS 16.225- **Factory vs Environment for DI?** -> Factory for services/repositories (app-wide). Environment for design-system values (colors, spacing).226- **Coordinator vs NavigationStack?** -> NavigationStack with a Router @Observable for most SwiftUI apps. UIKit Coordinator only for UIKit-heavy projects.227- **When to add TCA?** -> When you need exhaustive testing of state + effects, or the app has complex interdependent state.228- **When to modularize?** -> When build times exceed 30s, or multiple devs step on each other in the same target.229230---231232## References233234Read the appropriate reference file for detailed patterns, code examples, and implementation guidance:235236- `references/mvvm.md` -- MVVM with @Observable, ViewModel patterns, testing237- `references/clean.md` -- Clean Architecture layers, DI, Use Cases238- `references/tca.md` -- The Composable Architecture patterns239- `references/modular.md` -- SPM modules, feature modules, build optimization240- `references/patterns.md` -- Repository, Coordinator, error handling, POP, DI, code organization241242## Related Skills243- `ios-swiftui-expert` — SwiftUI implementation244- `swift-concurrency-expert` — async patterns245- `clean-architecture` — architectural principles246247## GitNexus Index248This skill is indexed by GitNexus for knowledge graph traversal.249Index path: /Users/localuser/.claude/skills/ios-architecture/.gitnexus250Last indexed: 2026-05-23
UltronCore