app-clip

Generate iOS App Clip targets with invocation URL handling and experience routing.

27|5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/bocan/bocan-music --skill app-clip-bocan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-clip
Source: https://github.com/bocan/bocan-music/tree/main/.claude/skills/generators/app-clip
Command: npx skills add https://github.com/bocan/bocan-music --skill app-clip-bocan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious and error-prone manual setup of iOS App Clips, which requires coordinating invocation URLs, Associated Domains, AASA files, location confirmation flows, and full app upgrade prompts while strictly adhering to Apple's 10 MB size limit and ephemeral data lifecycle.

Core Features & Use Cases

  • Complete Target Generation: Creates the @main App struct, invocation URL parser, experience routing protocol, and concrete implementations for ordering, reservations, check-ins, and content previews.
  • Physical World Integration: Includes optional CoreLocation-based location confirmation and Apple App Clip Code generation for NFC tags and QR codes.
  • Seamless Upgrade Path: Provides SKOverlay banners and App Group-backed data sharing to migrate user activity from the 8-hour ephemeral App Clip to the persistent full app.
  • Use Case: A coffee shop can deploy an App Clip that lets customers order from an NFC tag, confirms their physical presence, and prompts them to download the full app for loyalty rewards and order history.

Quick Start

Use the app-clip skill to generate a complete App Clip target with NFC and QR invocation, location confirmation, and a full app upgrade banner for your iOS project.

Frequently Asked Questions about app-clip

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

FAQPage Schema
How do I generate an iOS App Clip target with invocation URL handling?

Generating an iOS App Clip target involves creating the @main App struct, an invocation URL parser, and experience routing for tasks like ordering or reservations. This setup supports instant app experiences triggered via NFC tags, QR codes, or Safari banners.

How does an App Clip share data with a full app after an upgrade?

An App Clip shares data with a full app by utilizing App Group-backed data persistence. This mechanism migrates user activity from the ephemeral App Clip experience to the persistent full app, ensuring continuity alongside SKOverlay upgrade prompts.

Does an App Clip require Associated Domains and AASA configuration?

Yes, an App Clip requires Associated Domains and AASA configuration to satisfy Apple's technical requirements. These configurations are essential for properly routing invocation URLs from physical triggers like NFC tags and QR codes to the correct App Clip experience.

What is the binary size limit for a production-ready App Clip?

The binary size limit for a production-ready App Clip is strictly 10 MB. This budget requires careful size management to ensure the lightweight experience fits within Apple's constraints for instant app downloads.

Can I add location confirmation to an App Clip for physical world interactions?

Yes, you can add location confirmation to an App Clip using CoreLocation. This feature validates a user's physical presence near an NFC tag or QR code, which is useful for scenarios like check-ins or localized food ordering.

What is the best way to prompt users to download a full app from an App Clip?

The best way to prompt a full app download from an App Clip is using an SKOverlay banner. It provides a seamless upgrade interface that encourages users to install the complete application while preserving their current activity through App Group data sharing.