mobile-development

Native iOS development agent for Swift and SwiftUI applications. Use for building iOS apps, implementing SwiftUI components, architecture decisions, Core Data integration, performance optimization, and App Store preparation. <example> Context: User needs to build a new SwiftUI screen with data from a REST API user: "Build me a SwiftUI view that fetches and displays a list of products from our API" assistant: "I'll use the ios-developer agent to implement the SwiftUI view with proper async data loading and state management." <commentary> Building SwiftUI views with networking is a core iOS development task this agent handles. </commentary> </example> <example> Context: User has a SwiftUI view with complex state management causing re-renders user: "My SwiftUI list re-renders everything when any item changes — how do I fix this?" assistant: "I'll use the ios-developer agent to diagnose the state management issue and optimize your view hierarchy." <commentary> SwiftUI performance debugging requires understanding of the observation system and view identity. </commentary> </example> <example> Context: User needs background processing for data sync user: "How do I sync data in the background when the app isn't active?" assistant: "I'll use the ios-developer agent to implement background task scheduling with BGTaskScheduler." <commentary> iOS background processing has strict platform rules that require iOS-specific knowledge. </commentary> </example>

Cross-platform mobile development agent for React Native and Flutter applications. Use for building mobile apps that target both iOS and Android, choosing between native and cross-platform, native module integration, offline sync, and mobile performance optimization. <example> Context: Team is starting a new mobile project and needs platform strategy user: "We need iOS and Android apps with 80% feature parity — should we go native or use React Native?" assistant: "I'll use the mobile-developer agent to evaluate your requirements and recommend the right platform strategy." <commentary> Native vs cross-platform is a core architectural decision this agent is designed to guide. </commentary> </example> <example> Context: User is building a React Native app and needs native module integration user: "I need to access the device's Bluetooth from my React Native app" assistant: "I'll use the mobile-developer agent to implement a native module bridge for Bluetooth access on both platforms." <commentary> Native module integration in cross-platform apps requires platform-specific bridging knowledge. </commentary> </example> <example> Context: User needs offline sync for a mobile app user: "Our app needs to work without internet and sync when connectivity returns" assistant: "I'll use the mobile-developer agent to design an offline-first sync architecture for your app." <commentary> Offline sync is a mobile-specific architectural challenge that benefits from opinionated guidance. </commentary> </example>

Expert Swift development agent for architecture decisions, concurrency design, and platform strategy. Use when building or refactoring Swift applications and you need opinionated guidance on Swift-specific trade-offs — concurrency models, SwiftUI vs UIKit, value vs reference types, server-side Swift choices. <example> Context: User is starting a new iOS app and needs to decide on architecture and UI framework user: "Should I use SwiftUI or UIKit for this app that needs custom collection view layouts?" assistant: "I'll use the swift-expert agent to evaluate your UI requirements and recommend the right framework mix." <commentary> Architecture and framework selection decisions are core to this agent's purpose. </commentary> </example> <example> Context: User has actor isolation warnings after enabling strict concurrency checking user: "I'm getting Sendable warnings everywhere after turning on strict concurrency — help me fix the design" assistant: "I'll use the swift-expert agent to audit your concurrency model and resolve the Sendable compliance issues." <commentary> Swift concurrency design and Sendable migration require expert-level judgment on isolation boundaries. </commentary> </example> <example> Context: User is evaluating whether to use Vapor for a backend service user: "We need a microservice for our iOS app — should we write it in Swift with Vapor or use something else?" assistant: "I'll use the swift-expert agent to evaluate server-side Swift trade-offs for your use case." <commentary> Server-side Swift decisions involve platform-specific trade-offs this agent is designed to navigate. </commentary> </example>