ios-development
iOS development guidelines and best practices for the mobile-dev team
What this skill does
# iOS Development Guidelines ## Swift and SwiftUI Fundamentals - Use Swift 5.9+ with modern language features - Prefer SwiftUI for new UI components - Use property wrappers (@State, @Binding, @ObservedObject, @StateObject) appropriately - Leverage async/await for asynchronous operations - Use Swift concurrency actors for thread-safe code - Follow Swift API design guidelines ## UIKit and AppKit Patterns - Maintain compatibility with UIKit where needed - Use view controllers with proper lifecycle management - Implement Auto Layout constraints correctly - Use delegation and notification patterns appropriately - Handle memory management with ARC best practices - Use storyboards and XIBs sparingly; prefer programmatic UI ## iOS Architecture Patterns - **MVVM**: Use for SwiftUI-based applications - **MVC**: Use for UIKit-based applications - **Coordinator**: Use for complex navigation flows - Implement dependency injection for testability - Separate business logic from UI code - Use protocols for abstraction and testing ## Core Data and Persistence - Use Core Data for complex data models - Consider SwiftData for SwiftUI applications - Use UserDefaults for simple key-value storage - Implement proper data migration strategies - Use background contexts for heavy operations - Follow Core Data best practices for performance ## iOS Frameworks - **Combine**: Use for reactive programming - **SwiftUI**: Use for declarative UI - **ARKit**: Use for augmented reality features - **CoreML**: Use for machine learning integration - **MapKit**: Use for mapping and location - **CoreLocation**: Use for GPS and location services - **AVFoundation**: Use for media capture and playback - **WidgetKit**: Use for home screen widgets ## App Store Submission and Review Guidelines - Follow App Store Review Guidelines - Implement proper in-app purchase handling - Use App Store Connect for distribution - Prepare screenshots and metadata - Test on TestFlight before release - Handle app updates and versioning properly - Comply with privacy and data collection policies ## iOS Performance Optimization - Use Instruments for profiling - Optimize image assets and use asset catalogs - Implement lazy loading for large lists - Use caching strategies appropriately - Optimize network requests and data transfer - Reduce app launch time - Manage memory efficiently to avoid crashes ## Human Interface Guidelines - Follow Apple's Human Interface Guidelines - Support Dynamic Type for accessibility - Implement proper color contrast - Use SF Symbols for icons - Support VoiceOver for screen readers - Implement haptic feedback appropriately - Design for different screen sizes and orientations - Support Dark Mode properly
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.