linkrunner-ioslisted

Integrate the Linkrunner mobile attribution SDK into a native iOS (Swift) app - add the package via SPM, initialize it, identify users, track events and revenue, and set up deep linking (Universal Links and custom URL schemes) with domain verification. Use when someone asks to add Linkrunner to an iOS app, wire up attribution, or debug why Linkrunner deep links are not opening the app.
linkrunner-labs/skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill linkrunner-labs/skills

# Linkrunner - iOS (native) integration You are integrating **Linkrunner** (mobile attribution + deep linking) into a native iOS Swift app. Work in this order and **inspect the project before editing** - do not paste snippets blindly. ## 0. Before you touch anything 1. Confirm this is a native iOS app: there is an `.xcodeproj` or `.xcworkspace` and either a `Package.swift` or Xcode-managed Swift Package dependencies. 2. Find the app's entry point - the `@main` `App` struct (SwiftUI) or `AppDelegate`/`SceneDelegate` (UIKit) - and how it currently initializes. 3. Ask the user for their **project token** (dashboard -> Settings). If they use SDK signing, also get `secretKey` + `keyId`. Never hardcode these in a file that gets committed if the user keeps secrets elsewhere - ask where. 4. Check current versions against requirements (below) before bumping anything. ## 1. Decide what the user actually needs | They want... | Do this | | --- | --- | | "Add Linkrunner / set up attribution" | `references/install.md` then `references/events.md` (at minimum init + signup) | | "Set up deep links" / "links open Safari not my app" | `references/deep-linking.md` + run `scripts/verify-deeplinks.sh` | | "Track purchases / events" | `references/events.md` | Most first-time integrations need **install -> init -> signup -> handle deeplink**, in that order. Deep-link *verification* (AASA) is separate and is the part that usually breaks - treat it as its own step. ## 2. Requirem