app-clips

Configure iOS App Clip targets, invocation URLs, and App Store Connect experiences.

Updated May 10, 2026
One-click install
npx skills add https://github.com/FelixRauch/medat-figuren --skill app-clips-felixrauch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-clips
Source: https://github.com/FelixRauch/medat-figuren/tree/main/.agents/skills/app-clips
Command: npx skills add https://github.com/FelixRauch/medat-figuren --skill app-clips-felixrauch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of delivering lightweight iOS app entry points that open correctly via invocation URLs and physical codes, while keeping binaries small and handling the App Clip’s ephemeral lifecycle safely.

Core Features & Use Cases

  • App Clip target setup & shared code: Configure a dedicated App Clip target, bundle identifiers, embed settings, and conditional compilation to share implementation with the full app.
  • Invocation URL handling (NSUserActivity): Route web browsing invocations through onContinueUserActivity and extract context from URLs to drive the correct UI state.
  • Distribution, experiences, and QR/NFC/Messages: Set up default, demo, and advanced experiences with associated domains and AASA so that multiple entry points can map to the right App Clip behavior.
  • Data migration to the full app: Persist critical user/session/order data via shared App Group storage (and optionally shared Keychain) so installing the full app continues seamlessly.
  • Full-app promotion with SKOverlay: Recommend installing the full app after the user completes a task without interrupting them.
  • Optional location confirmation: Verify physical presence using APActivationPayload and NSAppClipRequestLocationConfirmation with lightweight constraints.

Quick Start

Use the app-clips skill to set up your App Clip target, register invocation handling with onContinueUserActivity, and configure an App Store Connect experience plus associated domains so QR/NFC and links open the correct in-clip context.

Frequently Asked Questions about app-clips

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

FAQPage Schema
How do I handle iOS App Clip invocation URLs with NSUserActivity?

iOS App Clip invocation URLs are handled by routing web browsing activities through `onContinueUserActivity` and extracting context from the URL to drive the correct UI state. This ensures the App Clip opens to the precise screen the user expects.

How do I migrate user session data from an App Clip to the full app?

Migrate user session data from an App Clip to the full app by persisting critical information via shared App Group storage and optionally shared Keychain. This allows the full app installation to continue seamlessly from where the App Clip left off.

What are the binary size limitations for an iOS App Clip?

iOS App Clips require strict binary size management to ensure the lightweight experience downloads and opens instantly. You must carefully manage assets and shared code to keep the App Clip bundle within Apple's strict size constraints.

Can I configure multiple App Clip experiences for different QR codes and NFC tags?

Yes, you can configure multiple App Clip experiences through App Store Connect using associated domains and AASA. This allows different QR codes, NFC tags, and URLs to map to specific App Clip behaviors and UI states.

How do I promote the full app inside an App Clip without interrupting the user?

Promote the full app inside an App Clip using SKOverlay. This presents an overlay banner recommending the full app installation after the user completes a task, without interrupting their current workflow.

Do I need a separate Xcode target to create an iOS App Clip?

Yes, creating an iOS App Clip requires setting up a dedicated Xcode target with correct entitlements and bundle relationships. You use conditional compilation to share implementation code between the App Clip and the full app.