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.
What this skill does
# 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 - [MVVM-C & VIP Implementation](references/implementation.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.