clerk-swift

Implement Clerk authentication in native Swift/iOS apps using clerk-ios.

66|4|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/clerk/skills --skill clerk-swift-clerk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-swift
Source: https://github.com/clerk/skills/tree/main/skills/mobile/clerk-swift
Command: npx skills add https://github.com/clerk/skills --skill clerk-swift-clerk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a deterministic, source-driven workflow to add or audit Clerk authentication in native Swift/iOS projects, removing guesswork about package versions, environment capabilities, and quickstart prerequisites.

Core Features & Use Cases

  • Source-driven installation: Inspect the installed clerk-ios package to determine required products and version constraints before adding or updating dependencies.
  • Prebuilt and custom flows: Support both ClerkKitUI prebuilt AuthView integrations and ClerkKit-based custom flows while enforcing AuthView parity rules for custom implementations.
  • Environment and quickstart audit: Map ClerkKitUI Environment fields, call /v1/environment after inspection, and verify/apply quickstart prerequisites including Associated Domains and Sign in with Apple capability.
  • Use Case: Convert a plain Swift app into a Clerk-authenticated iOS app by choosing prebuilt or custom flow, wiring a real publishable key, installing correct clerk-ios products, and completing quickstart-required capabilities.

Quick Start

Confirm the project is native iOS, choose prebuilt or custom flow, provide a real Clerk publishable key, and ask the agent to implement the selected flow using the installed clerk-ios package.

Frequently Asked Questions about clerk-swift

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add Clerk authentication to a native iOS Swift app?

Add Clerk authentication to a native iOS Swift app by installing the clerk-ios package, providing a publishable key, and wiring either ClerkKitUI prebuilt AuthView flows or custom ClerkKit components into your Xcode project.

What is the difference between ClerkKitUI and ClerkKit for iOS authentication?

ClerKitUI provides prebuilt AuthView screens for rapid integration, while ClerkKit enables custom authentication flows requiring AuthView parity rules to maintain environment capability consistency across your iOS application.

Does Clerk authentication for iOS require Sign in with Apple and Associated Domains?

Yes, Clerk authentication for iOS requires Sign in with Apple capability and Associated Domains configuration as quickstart prerequisites to ensure secure native authentication workflows.

How do I configure the Clerk environment in a Swift project?

Configure the Clerk environment in a Swift project by inspecting the installed clerk-ios package source to map ClerkKitUI Environment fields, then calling the /v1/environment endpoint to verify capabilities.

What version constraints should I use when installing the clerk-ios Swift package?

Install the clerk-ios Swift package products using up-to-next-major version requirements after inspecting the package source to determine the correct products needed for your chosen authentication flow.

Can I use Clerk prebuilt authentication UI with a custom Swift implementation?

You can use Clerk prebuilt ClerkKitUI alongside custom ClerkKit implementations, but custom flows must enforce AuthView parity rules to ensure environment fields and capabilities remain synchronized.