swift-tothemax

Pass Apple App Review the first time and recover fast when rejected. USE THIS SKILL whenever the user is submitting to the App Store, preparing a submission, asks 'will this get rejected', mentions App Review, a rejection, Resolution Center, an appeal, or any guideline number (2.1, 2.3, 3.1.1, 4.3, 5.1.x, etc.); whenever they set up TestFlight external testing / Beta App Review; whenever they want pre-submission checks, QC, demo accounts, reviewer notes, metadata or screenshot review; and whenever they ask IAP/paywall/subscription questions framed as compliance ('is this allowed', 'can I link to my website for payment'). Covers rejection playbooks, monetization compliance (US anti-steering + EU DMA state as of mid-2026), and an archive-to-approval checklist. Defer privacy manifests, GDPR, and legal document drafting to apple-legal-max; defer versioning, phased release, and release automation to apple-release-ops.

Orchestrator for the swift-tothemax plugin — routes any Apple-platform development task (building an iOS/macOS app, adding a feature, preparing a release, fixing a rejection) to the right combination of skills in the correct order. Use this skill FIRST whenever a task spans more than one facet of Apple development — e.g. "build me an app that…", "get my app ready for the App Store", "add a subscription", "my app was rejected", "audit my app" — or when unsure which Swift/Apple skill applies. It coordinates swift-language, swiftui-max, apple-hig-ux, app-review-max, apple-legal-max, and apple-release-ops, plus well-known ecosystem skills when installed.

Apple-platform design and UX judgment — what a good iOS/iPadOS/macOS/watchOS/visionOS app FEELS like. Use whenever designing app screens or flows, answering Human Interface Guidelines (HIG) questions, judging "does this feel native", running a UX review of an Apple-platform app, choosing navigation patterns (tabs vs hierarchy vs modal), designing onboarding, empty states, settings, or paywalls, doing accessibility audits, designing app icons or launch screens, handling dark mode, Liquid Glass adoption, typography, color, spacing, haptics, or UX copy. Trigger BEFORE writing SwiftUI for any new screen — design decisions come first. Complements swiftui-max (implementation) and app-review-max (App Store review); this skill owns design/UX judgment only.

Legal and privacy compliance for Apple-platform apps (iOS/iPadOS/macOS/watchOS/tvOS/visionOS). Use this skill WHENEVER a task touches - privacy policy, terms of service, ToS, EULA, license agreement, privacy manifest, PrivacyInfo.xcprivacy, required reason APIs, App Tracking Transparency, ATT, IDFA, tracking domains, privacy nutrition labels, App Privacy details, GDPR, CCPA/CPRA, US state privacy laws, COPPA, kids apps, children's privacy, age ratings, account deletion requirements, data deletion, export compliance, encryption declarations, ITSAppUsesNonExemptEncryption, France ANSSI declaration, EU DMA, alternative app marketplaces, web distribution, external purchase links, DSA trader status, subscription legal terms, or auto-renewal disclosures. Also use when drafting or reviewing ANY legal document or App Store Connect privacy/legal field for an app, when adding an SDK that collects data, or when a user asks "what legal stuff does my app need?" Sibling skill app-review-max owns App Review rejection mechan

The mechanics of shipping Apple apps. Use for ANY code signing error ("no signing certificate", "provisioning profile doesn't include...", "revoked certificate"), provisioning profiles, certificates, entitlements, capabilities, TestFlight (groups, expiry, feedback), App Store Connect, uploading builds, xcodebuild archive/-exportArchive, exportOptionsPlist, altool/ notarytool/Transporter, fastlane (match/gym/pilot/deliver), Xcode Cloud, CI/CD for iOS/macOS (GitHub Actions, keychains on runners), version and build numbers (agvtool, CURRENT_PROJECT_VERSION, MARKETING_VERSION), phased release and halting a rollout, app metadata and screenshots, App Store Connect API keys/webhooks, crash reports and crash spikes, and macOS notarization/stapling. Trigger on any release, distribution, or signing task — even a single cryptic Xcode signing error. NOT for App Review rejection strategy (use app-review-max) or privacy policies/legal (use apple-legal-max).

Comprehensive modern Swift (6.x) language expertise — concurrency, generics, ownership/performance, macros, API design, error handling, SwiftPM, C/C++/ObjC interop, cross-platform (Linux/Android/embedded/server), and Swift Testing. Use this skill whenever writing, reviewing, refactoring, or debugging ANY Swift code — even a single function — and whenever the user mentions Swift, .swift files, Xcode projects, Swift packages, actors, Sendable, swiftc, or compiler errors from a Swift build. Also use it when choosing between Swift language features or migrating code to a newer Swift version. Not needed for pure SwiftUI layout questions (a dedicated SwiftUI skill may fit better), but DO use it when SwiftUI code involves concurrency, performance, or general language questions.

Expert SwiftUI guidance for building UI on iOS, iPadOS, macOS, watchOS, tvOS, and visionOS. Use whenever writing, reviewing, refactoring, or debugging ANY SwiftUI code — views, view modifiers, layout, navigation (NavigationStack/SplitView, deep links), lists and scrolling, animation and transitions, state management (@State, @Binding, @Observable, Observation, environment), Liquid Glass adoption, toolbars, sheets and presentations, widgets/Live Activities, UIKit/AppKit interop, or SwiftUI performance problems (slow lists, hitches, excessive view updates). ALSO use it when building common UI components (bottom sheets, tab bars, onboarding, infinite scroll, skeletons, charts, forms, toasts), choosing or adding UI libraries (Pow, Lottie, Nuke, Kingfisher, snapshot testing, Inject hot reload, TCA), building a design system (tokens, themes, component packages), or iterating visually (simulator screenshots, previews, snapshot tests). Trigger on mentions of SwiftUI, "build a screen/view", "make it look good", @Obser

Autonomous UI crawler for iOS simulator apps — rapid, element-precise data collection. Use whenever the user says "crawl my app", "auto-test the UI", "click/tap through every screen", "monkey test", "explore the app and find errors/crashes", "collect screenshots of all screens", "smoke test the whole app", or asks for any app QA sweep, crash hunt, or screen inventory. It taps every reachable button/cell/switch via XCUITest, screenshots and journals every screen, detects crashes AS THEY HAPPEN with repro steps, streams console errors, and fans out cheap parallel Haiku subagents to label the haul. Data collection only — route fixes to swiftui-max/swift-language afterwards. Trigger even for a vague "is anything in my app broken?" — a crawl answers it empirically.