PassKit

Apple Wallet passes and Apple Pay on Apple platforms. The deep API reference — merchant setup, the full payment authorization flow, pass creation/library management, SwiftUI buttons, use cases, security — lives in references/guide.md. This file is the decision and discipline layer: read it first, open the guide for specifics.

Dials

Set these explicitly at the start; they change what "correct" means.

1. DOMAIN — wallet-passes (issue/add/manage PKPass in Wallet) · apple-pay (charge for physical goods/services via PKPaymentRequest) · both. Apple Pay and Wallet passes are unrelated subsystems that happen to share the PassKit import; pick what you're actually building.
2. PASS_UPDATES — static (one-shot .pkpass, never changes) · push-updatable (pass has webServiceURL + authenticationToken, your server pushes updates via APNs and the Wallet web service protocol). Only relevant when DOMAIN includes wallet-passes.
3. PAY_UI — PayWithApplePayButton-SwiftUI (iOS 16+, default for SwiftUI; handles presentation via onPaymentAuthorizationChange) · PKPaymentButton-UIKit (PKPaymentAuthorizationController + delegate, for UIKit or full control). Only relevant when DOMAIN includes apple-pay.

When to use

Building or reviewing any Wallet-pass issuing/adding/updating code, or any Apple Pay payment sheet, request, or token-handling code. If the user wants to sell digital content (subscriptions, unlocks, consumables), that is StoreKit, not Apple Pay — use the storekit skill. Apple Pay is only for real-world goods and services.

Core rules