macos-extensionkit

Iterate on algorithmic trading strategies in ArgoTradingSwift (`.rxtrading` documents) via the embedded MCP server. Use when the user wants to write, build, backtest, or improve Go-based trading strategies that compile to WASM, load a `.wasm` strategy into the app, run a backtest against a schema/dataset, or analyze backtest results (stats.yaml + per-trade parquet). Triggers include phrases like "write a trading strategy", "backtest this strategy", "beat buy-and-hold", "load_strategy", "run_backtest", and any mention of argo-trading, ArgoTradingSwift, or `.rxtrading` files.

Manage the two-stage iOS release pipeline using GitHub Actions for CI/semantic versioning and Xcode Cloud for App Store distribution. Use when the user needs to (1) trigger a new iOS release, (2) understand or modify CI workflows (ios-ci.yml, ios-setup.yml, create-release.yaml), (3) debug version bumping or Xcode Cloud builds, (4) update the ci_post_clone.sh script, (5) configure or rotate CI secrets, (6) understand conventional commit conventions for version bumps, or (7) troubleshoot failed releases or TestFlight submissions.

Build a macOS app that hosts its own in-app UI extension using Apple's ExtensionKit / ExtensionFoundation (AppExtension, AppExtensionPoint, EXHostViewController, NSXPC). Use when creating a host app + bundled app-extension target, defining a custom extension point, sharing an API/XPC contract core between host and extension, embedding extension SwiftUI inside the host, wiring bidirectional host↔extension messaging, or debugging extension discovery/activation failures (OSStatus -10814, "Failed to get extension process and XPC endpoints", LSRegisterURL -10819).

Implement OAuth 2.0 authentication for Next.js backend and iOS Swift apps. Use when setting up OAuth/OIDC authentication, configuring Auth.js (NextAuth v5), implementing PKCE flow for iOS, adding Bearer token support, creating auth middleware, setting up token storage/refresh, or writing E2E tests with mock authentication. Covers the full auth stack from provider configuration through session management.

Set up and maintain OpenAPI 3.0 integration between a Next.js backend and a Swift iOS client. Use when the user needs to (1) set up OpenAPI spec generation from Zod schemas using next-openapi-gen, (2) configure Swift OpenAPI generator for an iOS package, (3) create or update API routes with JSDoc annotations, (4) create Zod schemas for API contracts, (5) sync the OpenAPI spec between backend and iOS, (6) create Swift service layers wrapping generated API clients, or (7) troubleshoot OpenAPI generation or Swift type issues.