agentleFS
EronredEronred/aso-skills/skills/app-clips/SKILL.md

app-clips

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.

2 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After using it, they see a banner: "Get the full app"

    line 54
  2. Distinctive:

    Only the core experience

    line 63
  3. Distinctive:

    No App Clip–only content — everything in the clip should also be in the full app

    line 65
  4. Distinctive:

    Always include a clear upgrade prompt:

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

App Clips

You help plan, implement, and optimize App Clips — lightweight iOS experiences (max 15MB) that users can launch instantly without installing the full app.

What App Clips Are

App Clips are small, focused pieces of your app that users can use without downloading the full app. They appear in:

  • App Store search results — alongside your full app
  • Smart App Banners on websites
  • QR codes and App Clip codes (physical NFC/QR)
  • Safari — when visiting a linked URL
  • Messages — when a URL is shared in iMessages
  • Maps — for location-based businesses
  • Nearby — NFC and visual codes in the physical world
  • Siri suggestions

Size Limit

TargetLimit
App Clip binary15MB max (thinned, downloaded on demand)
App itselfNo change

This forces you to ship only the essential experience.

Best Use Cases

App TypeApp Clip Experience
Parking/transitPay for parking or buy a ticket
RestaurantView menu, order, or pay
RetailProduct preview or loyalty card
FitnessTry a single workout
GamesPlay a demo level
FinanceCalculator or quick quote
EventsTicket purchase or check-in
UtilitiesUse core feature once

The key question: What is the minimum experience that demonstrates your app's core value?

App Clip Discovery in the App Store

App Clips appear in App Store search as a separate card below your full app result — labeled "App Clip" with an "Open" button (not "Get").

  • Users who tap "Open" launch the App Clip instantly
  • After using it, they see a banner: "Get the full app"
  • Conversion from App Clip user → full install is typically 3–5× higher than cold organic traffic

ASO implication: The App Clip card inherits your app's title and description metadata. Optimizing your main listing improves App Clip discoverability too.

Technical Requirements

What to include in the App Clip

  • Only the core experience
  • Apple Pay or Sign in with Apple for authentication (no full account creation)
  • No App Clip–only content — everything in the clip should also be in the full app
  • Request only essential permissions (no push notifications in App Clips)

URL scheme

Each App Clip is triggered by a URL:

https://yourdomain.com/clip/[experience]

Configure in App Store Connect → Your App → App Clip Experiences.

Handoff to Full App

Always include a clear upgrade prompt:

// Show SKOverlay after the user gets value from the clip
let config = SKOverlay.AppClipConfiguration(position: .bottom)
let overlay = SKOverlay(configuration: config)
overlay.present(in: windowScene)

Show the overlay after the user has experienced value — not immediately.

App Clip Experiences

You can configure multiple App Clip experiences (one per URL pattern):

ExperienceURLUse Case
Defaultyourdomain.comGeneral / App Store search
Locationyourdomain.com/location/123Maps, NFC at specific location
Campaignyourdomain.com/promo/summerMarketing campaign
Featureyourdomain.com/feature/xSpecific feature demo

Each experience can have its own:

  • Title (max 18 chars)
  • Subtitle (max 13 chars)
  • Header image (3000×2000px)
  • Action button text

App Clip Card Design

The card is shown before the App Clip launches:

FieldLimitTips
Title18 charsClear action: "Order Coffee" not "App Name"
Subtitle13 charsReinforce the value: "Skip the line"
Header image3000×2000pxShow the outcome, not the UI
Action button—Use context-specific text: "Order", "Pay", "Play"

Measurement

Track in App Store Connect → App Analytics → App Clips:

  • App Clip sessions
  • App Clip cards displayed
  • App Clip → full app conversions
  • Unique App Clip users

App Clip vs Full App Install Trade-offs

App ClipFull Install
User frictionVery lowHigher
CommitmentLowHigh
RetentionLow (one-time use)High
Conversion from Clip—3–5× higher than cold traffic
Best forDiscovery + conversionRetention + monetization

Implementation Checklist

Setup:
- [ ] App Clip target added to Xcode project
- [ ] App Clip < 15MB (use size report in Xcode)
- [ ] Associated Domains entitlement configured
- [ ] App Clip experience URLs registered in App Store Connect

UX:
- [ ] Core value delivered within 60 seconds
- [ ] Sign in with Apple or Apple Pay (no custom sign-up)
- [ ] SKOverlay shown post-value (not immediately)
- [ ] Clear data handoff when user installs full app

App Store Connect:
- [ ] Default App Clip experience configured
- [ ] Header image uploaded (3000×2000px)
- [ ] Title ≤ 18 chars, subtitle ≤ 13 chars
- [ ] Additional experiences for locations/campaigns (if applicable)

Related Skills

  • aso-audit — Clip discoverability depends on main app ASO
  • onboarding-optimization — Apply same "value-first" principles to Clip experience
  • ua-campaign — Drive traffic to App Clip URLs in paid campaigns
  • app-store-featured — App Clips can support featuring eligibility

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.