← ClaudeAtlas

cryptotokenkitlisted

Builds CryptoTokenKit security-token and smart-card integrations. Use for token-driver extensions, token sessions, TKSmartCard communication, NFC smart-card sessions, token-backed Keychain queries, token watching, certificate authentication, APDU handling, or PIN workflows.
thienqo/ios-skills · ★ 11 · AI & Automation · score 69
Install: claude install-skill thienqo/ios-skills
# CryptoTokenKit Use CryptoTokenKit for token-driver extensions, smart-card sessions, token-backed Keychain items, certificate authentication, and iOS/iPadOS 26+ NFC smart-card access. API presence is not an access guarantee: extension points, entitlements, hardware, and runtime support all matter. The login/keychain-unlock token extension flow is macOS-specific, `TKSmartCardSlotManager.default` is optional, and NFC smart-card slot creation requires iOS/iPadOS 26+. ## Contents - [Choose the workflow](#choose-the-workflow) - [Architecture and boundaries](#architecture-and-boundaries) - [Core invariants](#core-invariants) - [Platform and capability checks](#platform-and-capability-checks) - [Error handling](#error-handling) - [Common mistakes](#common-mistakes) - [Review checklist](#review-checklist) - [References](#references) ## Choose the workflow - For the macOS driver/token/session classes, extension Info.plist, PIN auth, low-level APDU sessions, token-backed Keychain queries, NFC slot lifecycle, and certificate requirements, read [Token and smart-card workflows](references/token-and-smart-card-workflows.md). - For PIV selection and signing, BER/compact TLV parsing, generic token drivers, command chaining, large responses, secure PIN operations, configuration, slot monitoring, and registration, read [CryptoTokenKit extended patterns](references/cryptotokenkit-patterns.md). ## Architecture and boundaries CryptoTokenKit has three distinct modes: 1. A mac