Ios Architecture

---
name: ios-architecture
description: iOS architecture orchestration for production apps, modular codebases, Swift patterns, scale practices, and release-ready implementation boundaries.
metadata:
  portable: true
  compatible_with:
  - claude-code
  - codex
---

# iOS Architecture
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

<!-- dual-compat-start -->
## Use When

- Designing, reviewing, or refactoring iOS app architecture, modular boundaries, dependency injection, navigation, production patterns, or large-team delivery.
- The task mentions MVVM, clean architecture, Swift patterns, UIKit/SwiftUI boundaries, modularization, scaling, CI impact, or maintainability.
- A narrow retired iOS architecture skill is referenced by name.

## Do Not Use When

- The request is only about general iOS implementation; use `ios-development`.
- The request is only about UI polish; use `ios-ui-ux-design`.
- The request is only about persistence, platform capabilities, quality/release, or security/RBAC; use those parent skills.

## Required Inputs

- App scope, platform targets, current module layout, UI framework mix, backend/API shape, team size, release constraints, and the concrete architectural decision or defect.
- Existing project files or diagrams when implementation or review is requested.

## Workflow

1. Load `ios-development` first for shared iOS implementation standards.
2. Identify the architecture concern: app composition, module boundaries, Swift patterns, scale practices, or production gotchas.
3. Load only the matching reference below.
4. Produce a concrete architecture decision, refactor plan, review finding, or implementation patch with tests and rollout notes when relevant.

## Quality Standards

- Architecture decisions must preserve platform-native UX, testability, dependency clarity, and predictable release behaviour.
- Module boundaries must have explicit ownership, public APIs, dependency direction, and migration steps.
- Any scale guidance must include CI, build-time, ownership, or observability impact when it changes delivery workflow.

## Anti-Patterns

- Creating abstract layers without a current complexity or testability problem.
- Mixing UIKit, SwiftUI, model state, and networking without clear ownership.
- Treating large-team practices as default for small apps.

## Outputs

- iOS architecture decision record, module map, refactor plan, review findings, or implementation guidance.

## References

- `references/ios-architecture-advanced.md` for dependency injection, MVVM variants, navigation, and testable architecture patterns.
- `references/ios-at-scale.md` for modularization, large-team workflows, build systems, and CI practices.
- `references/ios-production-patterns.md` for production UIKit/SwiftUI lifecycle and app-store-proven implementation rules.
- `references/ios-swift-design-patterns.md` for Swift-idiomatic patterns and reusable implementation recipes.
<!-- dual-compat-end -->