What problem does it solve? Adding authentication to a native iOS app with Clerk requires navigating package setup, environment configuration, quickstart prerequisites like associated domains, and choosing between prebuilt UI components or custom flows. This Skill guides that entire implementation by reading the installed clerk-ios package source so the result mirrors current ClerkKit and ClerkKitUI behavior. ## Core Features & Use Cases - Prebuilt Auth Flow: Wire up ClerkKitUI's AuthView in a sheet with UserButton signed-out entry, including Apple capability checks driven by the /v1/environment endpoint. - Custom Auth Flow: Build custom sign-in/sign-up screens with ClerkKit primitives while keeping step progression, field visibility, and layout close to AuthView defaults. - Quickstart Compliance Audit: Reads the iOS quickstart from the installed package README and applies missing setup such as the associated domain capability (webcredentials:{YOUR_FRONTEND_API_URL}). - Use Case: You are building a SwiftUI app and need sign-in with Apple plus email authentication. The Skill confirms your flow choice and publishable key, installs clerk-ios with an up-to-next-major requirement, inspects ClerkKitUI source, and implements the flow with all required capabilities. ## Quick Start Ask the assistant to add Clerk authentication to your native SwiftUI app, specifying whether you want prebuilt AuthView components or a custom flow along with your Clerk publishable key.
