swift-pro

Build the project via XcodeBuildMCP

Scaffold a complete feature module

Create a Product Requirements Document from discussion

Scaffold a SwiftUI view + ViewModel

Diagnose and fix build errors

macOS AppKit specialist. Use for NSWindow management, NSSplitViewController (3-pane layouts), NSOutlineView source lists, NSToolbar, menus and menu bar, and hosting SwiftUI views inside AppKit containers. Handles production macOS apps that need full native integration beyond what SwiftUI alone provides. Trigger on: "macOS," "AppKit," "NSWindow," "toolbar," "sidebar," "NSOutlineView," "NSSplitViewController," "menu," "menu bar," "NSToolbar," "source list," or any macOS-specific UI task. <example> Context: User wants a 3-pane macOS app layout user: "Build a 3-column macOS app with sidebar, content, and inspector" assistant: "I'll use the appkit-specialist agent to design the NSSplitViewController layout with SwiftUI content views." <commentary> Classic macOS 3-pane layout — appkit-specialist designs the window architecture. </commentary> </example> <example> Context: User needs a source list sidebar user: "Create a sidebar with expandable groups like Finder's sidebar" assistant: "I'll use the appkit-specialist agent to implement an NSOutlineView source list." <commentary> Source list implementation — appkit-specialist uses NSOutlineView for native behavior. </commentary> </example> <example> Context: User wants toolbar customization user: "Add a customizable toolbar with search, view mode, and share buttons" assistant: "I'll use the appkit-specialist agent to implement NSToolbar with proper item configuration." <commentary> Toolbar task — appkit-specialist builds NSToolbar with native macOS conventions. </commentary> </example>

Swift 6 concurrency specialist. Use for async/await patterns, actor isolation, Sendable conformance, @MainActor annotation, structured and unstructured concurrency, AsyncSequence, and fixing strict concurrency warnings. Every concurrency warning is a potential data race. This agent resolves them without suppression. Trigger on: "async," "await," "actor," "Sendable," "@MainActor," "concurrency warning," "data race," "Task," "TaskGroup," "AsyncSequence," "AsyncStream," or any Swift concurrency task. <example> Context: User has concurrency warnings after enabling strict checking user: "I'm getting 'Sending main actor-isolated value to nonisolated context' warnings everywhere" assistant: "I'll use the concurrency-specialist agent to diagnose and fix each warning systematically." <commentary> Concurrency warning resolution — the core use case for this agent. </commentary> </example> <example> Context: User needs to design an actor-based service user: "Design a thread-safe cache that can be used from any context" assistant: "I'll use the concurrency-specialist agent to design an actor-based cache with proper isolation." <commentary> Actor design task — concurrency-specialist designs the isolation boundary. </commentary> </example> <example> Context: User needs to process items in parallel user: "Download thumbnails for 50 items concurrently with a limit of 5 at a time" assistant: "I'll use the concurrency-specialist agent to implement a TaskGroup with concurrency throttling." <commentary> Structured concurrency with throttling — concurrency-specialist territory. </commentary> </example>

Swift networking specialist. Use for URLSession async/await, Codable encoding/decoding, token-based authentication (JWT refresh), retry logic, endpoint abstraction, typed errors, and async sequence streaming. Handles all network layer concerns from API client design to error handling. Trigger on: "URLSession," "networking," "API client," "Codable," "JSON," "JWT," "token refresh," "retry," "endpoint," "HTTP," "REST," "download," or any networking task. <example> Context: User wants to build an API client user: "Build a type-safe API client for our REST backend" assistant: "I'll use the networking-engineer agent to design the actor-based APIClient with typed endpoints." <commentary> API client design — networking-engineer builds the full networking layer. </commentary> </example> <example> Context: User needs JWT token refresh user: "Implement automatic token refresh when the API returns 401" assistant: "I'll use the networking-engineer agent to add JWT refresh logic to the API client." <commentary> Token auth task — networking-engineer handles the refresh dance. </commentary> </example> <example> Context: User needs to decode complex JSON user: "The API returns nested JSON with snake_case keys and optional fields" assistant: "I'll use the networking-engineer agent to write the Codable models with a custom decoder." <commentary> Codable task — networking-engineer designs the decoding strategy. </commentary> </example>

Apple platform integration specialist. Use for Spotlight indexing, WidgetKit extensions, Share Extensions, App Intents (Shortcuts), CloudKit, push notifications (APNs), App Groups, and StoreKit 2. Handles all system framework integration that extends the app beyond its main process. Trigger on: "Spotlight," "Widget," "Extension," "Shortcuts," "Intents," "CloudKit," "push notification," "APNs," "App Group," "StoreKit," "in-app purchase," or any platform integration task. <example> Context: User wants Spotlight search integration user: "Make claims searchable from the iOS Spotlight search" assistant: "I'll use the platform-integrator agent to implement CSSearchableItem indexing." <commentary> Spotlight integration — platform-integrator indexes domain objects for system-wide search. </commentary> </example> <example> Context: User wants a home screen widget user: "Create a widget showing recent claims on the home screen" assistant: "I'll use the platform-integrator agent to build the WidgetKit extension with a TimelineProvider." <commentary> Widget creation — platform-integrator builds the timeline provider and widget views. </commentary> </example> <example> Context: User wants Siri Shortcuts integration user: "Let users add a claim via Siri using App Intents" assistant: "I'll use the platform-integrator agent to implement the App Intent and parameter resolution." <commentary> App Intents task — platform-integrator defines the intent, parameters, and perform method. </commentary> </example>

Core Swift architecture agent and plugin hub. Use for app scaffolding, MVVM with @Observable, NavigationStack routing, module structure, dependency injection, and general architecture decisions. This is the default entry point for any Swift task. It routes to specialized agents when deeper expertise is needed (swiftui-builder for views, swiftdata-engineer for persistence, concurrency-specialist for async/actors, platform-integrator for system frameworks, networking-engineer for API clients, appkit-specialist for macOS, test-engineer for testing). Trigger on: any Swift app request, "build an app," "create a feature," "architecture," "MVVM," "navigation," "module structure," "dependency injection," or general Swift project questions. <example> Context: User wants to start a new iOS app user: "Build a knowledge graph app for iOS with SwiftData persistence" assistant: "I'll use the swift-architect agent to design the app architecture, module structure, and navigation hierarchy." <commentary> New app scaffold — swift-architect designs the foundation, then routes to swiftdata-engineer for models and swiftui-builder for views. </commentary> </example> <example> Context: User asks about structuring a feature module user: "How should I structure the search feature with its own ViewModel and views?" assistant: "I'll use the swift-architect agent to design the feature module with MVVM and @Observable." <commentary> Feature architecture question — swift-architect defines module boundaries, ViewModel shape, and view hierarchy. </commentary> </example> <example> Context: User needs navigation architecture user: "Set up type-safe navigation with deep linking support" assistant: "I'll use the swift-architect agent to design the NavigationStack routing layer." <commentary> Navigation design — swift-architect owns the routing enum and NavigationStack configuration. </commentary> </example>

1 hook across 1 event