passkitlisted

# PassKit — Foundations Skill ## Purpose Route PassKit implementation tasks to the minimum required PassKit Knowledge Contracts. v1 scope is app-side Wallet-pass querying/adding, `.pkpass`/`pass.json` structure, the add-to-Wallet UI flow, the app-vs-server pass-update boundary, and building/presenting Apple Pay -- not server-side pass signing or certificate management, not NFC/secure-element passes, not pass personalization, and not Apple Pay's server-side merchant validation or token decryption. ## Routing Load only the contracts relevant to the task. All paths relative to knowledge/passkit/. - Calling `PKPassLibrary.isPassLibraryAvailable()`/`containsPass(_:)`/`passes()`/`passes(of:)`; adding held passes with `addPasses(_:withCompletionHandler:)`; or asking why there's no EventKit-style permission gate -> pass-library-and-authorization.md - Authoring or validating `pass.json` (`formatVersion`/`passTypeIdentifier`/`serialNumber`/`teamIdentifier`/`organizationName`/`description`, the `boardingPass`/`coupon`/`eventTicket`/`storeCard`/`generic` style keys, `PassFields` groups, `barcodes`, `locations`/`relevantDates`); or inspecting a pass with `PKPass(data:)` -> pass-content-and-required-fields.md - Presenting `AddPassToWalletButton` (SwiftUI) or `PKAddPassesViewController`/`PKAddPassButton` (UIKit); checking `canAddPasses()`; or the delegate/dismissal pattern -> adding-passes-ui.md - Wiring `webServiceURL`/`authenticationToken`; or understanding the device-registr