Axiom

Use when the user mentions App Store screenshot validation, screenshot review, checking screenshots before submission, or verifying screenshot dimensions and content.

Use when the user mentions simulator testing, visual verification, push notification testing, location simulation, screenshot capture, OR live accessibility validation (VoiceOver announcements, Dynamic Type, ADA checks) on the simulator.

Use when the user wants to simplify Swift code, reduce boilerplate, or make Swift more readable and idiomatic without changing behavior.

Use when the user mentions security review, App Store submission prep, Privacy Manifest requirements, hardcoded credentials, or sensitive data storage.

Use when the user wants to run XCUITests, parse test results, view test failures, or export test attachments.

Use when the user mentions SPM resolution failures, "no such module" errors, duplicate symbol linker errors, version conflicts between packages, or Swift 6 package compatibility issues.

Use when the user wants automated performance profiling, headless Instruments analysis, or CLI-based trace collection.

Use when the user mentions slow builds, build performance, or build time optimization.

Use when the user wants to modernize iOS code to iOS 17/18 patterns, migrate from ObservableObject to @Observable, update @StateObject to @State, or adopt modern SwiftUI APIs.

Use when the user wants to add in-app purchases, implement StoreKit 2, or set up subscriptions.

Use when the user wants a comprehensive project-wide audit, full health check, or scan across all domains.

Use when the user mentions Xcode build failures, build errors, or environment issues.

Use this agent for closed-loop test debugging - automatically analyzes test failures, suggests fixes, and re-runs tests until passing.

Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.

Use when the user mentions TextKit review, text layout issues, Writing Tools integration, or UITextView/NSTextView code review.

Use when the user wants to audit test quality, find flaky test patterns, speed up test execution, or prepare for Swift Testing migration.

Use when the user mentions SwiftUI navigation issues, deep linking problems, state restoration bugs, or navigation architecture review.

Use when the user mentions SwiftUI layout review, adaptive layout issues, GeometryReader problems, or multi-device layout checking.

Use when the user mentions SwiftUI architecture review, separation of concerns, testability issues, or "logic in view" problems.

Use when the user mentions SwiftData review, @Model issues, SwiftData migration safety, or SwiftData performance checking.

Use when the user mentions file storage issues, data loss, backup bloat, or asks to audit storage usage.

Use when the user wants to audit SpriteKit game code for common issues.

Use when the user mentions window resizing support, resizable-window readiness, iPhone Mirroring compatibility, scene-lifecycle migration checking, or preparing an app for the 27-cycle resizing model.

Use when the user mentions networking review, deprecated APIs, connection issues, or App Store submission prep.

Use when the user mentions memory leak prevention, code review for memory issues, or proactive leak checking.