ios-architecture
iOS architecture orchestration for production apps, modular codebases, Swift patterns, scale practices, and release-ready implementation boundaries.
Best use case
ios-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
iOS architecture orchestration for production apps, modular codebases, Swift patterns, scale practices, and release-ready implementation boundaries.
Teams using ios-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ios-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ios-architecture Compares
| Feature / Agent | ios-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
iOS architecture orchestration for production apps, modular codebases, Swift patterns, scale practices, and release-ready implementation boundaries.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 -->
Related Skills
saas-architecture-strategy
Use when architecting or evaluating a cloud SaaS product — including choosing multi-tenant patterns, mapping deployment to IaaS, planning scaling and blast-radius isolation, aligning architecture to business capabilities, and reconciling multi-enterprise consumption requirements with operating-model constraints.
multi-tenant-saas-architecture
Use when designing or reviewing a multi-tenant SaaS platform — tenant isolation model, three-panel separation (super admin, franchise admin, end user), zero-trust enforcement, audit trails, and per-tenant permission overrides. Unlike `modular-saas-architecture` which focuses on pluggable business modules, this skill defines the tenancy and auth boundaries that every module inherits.
modular-saas-architecture
Build SAAS platforms with pluggable business modules (Advanced Inventory, Restaurant, Pharmacy, etc.) that can be enabled/disabled per tenant without breaking the system. Use when designing modular SAAS features, implementing module toggles...
cloud-architecture
Use when designing cloud deployments, Dockerising applications, laying out AWS or GCP environments, choosing a deployment pattern, or moving a workload from a single VM to a resilient multi-AZ topology.
system-architecture-design
Use when defining or reviewing software architecture for web apps, mobile backends, SaaS platforms, APIs, distributed systems, or major features. Covers bounded contexts, module decomposition, contracts, failure handling, ADRs, and scalability tradeoffs.
microservices-architecture
Use when designing, reviewing, or refactoring microservice boundaries, communication, service ownership, deployment independence, resilience, and distributed data flows. Load absorbed microservices fundamentals, models, communication, and resilience references as needed.
ai-app-architecture
Use when designing or building AI-powered application systems — choosing architecture style, selecting components, structuring the AI stack, making build-vs-buy decisions, and planning multi-tenant AI module gating
ai-agent-runtime-architecture
Use when designing the runtime that hosts agentic LLM features in a multi-tenant SaaS — the agent loop as a control-plane service, formal state machine (PERCEIVE → PLAN → ACT → OBSERVE), retries, idempotency, max-step caps, deterministic resumability, and the "agent vs workflow vs cron" decision. Distinct from `ai-agents-tools` (agent fundamentals) and `ai-on-saas-architecture` (overall AI architecture).
web-app-security-audit
Use when auditing a PHP/JavaScript/HTML web application for security vulnerabilities. Covers configuration, authentication, authorization, input validation, XSS, API security, HTTP headers, and dependency scanning. Produces a severity-rated audit...
vibe-security-skill
Use when designing or reviewing security for a web application, API, or multi-tenant SaaS — produces threat model, abuse case list, auth/authz matrix, and secret handling plan; covers OWASP Top 10 2025 and the AI-code-generation blind spots. Neighbours — api-design-first owns auth model fields, deployment-release-engineering owns secret rotation choreography, ai-security and llm-security own model-specific threats.
network-security
Use when designing, hardening, or auditing network-layer security for self-managed Debian/Ubuntu SaaS infrastructure — firewalls (nftables/UFW), WAF (ModSecurity + OWASP CRS), VPN (WireGuard, OpenVPN, IPsec), TLS/PKI ops, IDS/IPS (Suricata, Fail2ban), zero-trust, SSH hardening, DDoS mitigation, DNS security. Complements web-app-security-audit (app layer) and cicd-devsecops (secrets/CI).
linux-security-hardening
Use when hardening a Debian/Ubuntu server — user/group/sudo hardening, file permission audits, PAM password policy + MFA, AppArmor mandatory access control, auditd system call logging, kernel sysctl hardening, file integrity monitoring (AIDE), rootkit detection (rkhunter/chkrootkit), unattended security patching, GRUB + UEFI + LUKS boot security, and CIS benchmark compliance.