skills/ HoangNguyen0403/agent-skills-standard

ios-architecture

Apply MVVM, Coordinators, and Clean Architecture (VIP/VIPER) in iOS apps. Use when applying MVVM, Coordinators, or VIP/VIPER architecture in iOS apps.

0
Installs
—
Rating
—
Success rate
3
Files scanned
Scan passedmobile
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

3 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 608a20102b9f99e9… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

iOS Architecture Standards

Priority: P0 (CRITICAL)

Implementation Guidelines

MVVM (Model-View-ViewModel)

  • ViewModel Responsibility: Handle business logic, formatting, and state. No UIKit imports (except for platform types like UIImage if strictly necessary).
  • ViewState: Use single state object or discrete @Published properties for UI updates. Expose state as private(set) or using publishers.
  • Inputs/Outputs: Define explicit protocols or nested types for inputs (events from View) and outputs (state for View).

Coordinator Pattern

  • Navigation Logic: Decouple ViewControllers from navigation logic. Coordinator handles instantiation and push/present. ** NOT use navigationController directly in ViewController for screen transitions.**
  • Dependency Injection: Pass dependencies (Services, Repositories) through Coordinator into ViewModels.
  • Child Coordinators: Maintain hierarchy; correctly remove child coordinators from parent's collection when their flow finished.

Clean Architecture (VIP/VIPER)

  • VIP (Clean Swift): Use Interactor for logic, Presenter for UI formatting, and ViewController for display.
  • Unidirectional Flow: Data flows: View -> Interactor -> Presenter -> View.
  • VIPER: (View, Interactor, Presenter, Entity, Router) — another common architectural pattern for iOS apps.

Anti-Patterns

  • No Logic in VC: Move business logic to ViewModel/Interactor.
  • No Public ViewModel State: Keep state private(set) or using publishers.
  • No Direct Navigation: Use Coordinator for screen transitions. Never use navigationController directly.

Verification Checklist (Mandatory)

  • Pure ViewModel: ViewModel any UIKit imports? (Prohibited)
  • Navigation: navigationController used directly in VC for transitions? (Use Coordinator)
  • State Access: ViewModel state exposed as public var? (Use private(set) or publishers)
  • Deallocation: child coordinators correctly removed from parent's collection on finish?
  • VIP Unidirection: data flow unidirectional (View -> Interactor -> Presenter -> View)?

References

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

  • Inputs/Outputs
  • UIImage
  • ViewModel Responsibility

Remediation anchors

  • Remediation anchors: ViewState, @Published, explicit Inputs/Outputs

Files

3
6.8 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related mobile skillsscan passed