agentleFS
moasqmoasq/ios-dev-agent/.agents/skills/onboarding/SKILL.md

onboarding

Skill4 starsChanged 6 months agoMITView on GitHub

Use when building, improving, or auditing iOS onboarding screens, first-run activation, conversion flow, onboarding copy, or paywall lead-in strategy.

100 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 19 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 18 projects that use this

  • +7 more from Cesarjoquin

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 13

    Distinctive

    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:

    If removing a screen doesn't reduce conversion, it shouldn't exist.

    line 22
  2. Distinctive:

    If a question doesn't change anything, remove it

    line 40
  3. Distinctive:

    No explanation needed. Minimal text.

    line 46
  4. Distinctive:

    If real: show genuine progress with fun facts

    line 50
  5. Distinctive:

    If fake: users detect it — kills trust.

    line 51
  6. Distinctive:

    Every bullet references THEIR specific results

    line 63
  7. Distinctive:

    Must feel like natural next step, not a wall

    line 70
  8. Distinctive:

    When launching with zero ratings and zero users:

    line 87
  9. Distinctive:

    Do NOT add fake testimonials or star ratings

    line 88
  10. Distinctive:

    Do NOT say "trusted by X users" or "4.9 stars"

    line 89
  11. Distinctive:

    DO let the product speak: the personalized analysis is more convincing than any review

    line 90
  12. Distinctive:

    DO add social proof AFTER you have real reviews (10+ ratings)

    line 91
  13. Distinctive:

    NEVER during onboarding. NEVER on first session.

    line 104

“Common” is measured: kept by at least 6 in 10 of the 85 edited versions of this file we could read. “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

Mobile App Onboarding — Conversion-Optimized Design

Design onboarding flows that convert installs into subscribers. Every screen earns its place or gets cut.

Core Principles

1. TikTok Brain Rule

Each screen: 5-7 words max for headline. Users scan, they don't read. Design for thumb taps, not paragraphs. Every screen is a micro-conversion — one tap, one swipe, one record.

2. Interactive > Passive

Screens where the user DOES something (taps, selects, records) retain 3x better than screens where they READ something. Kill explainer carousels. Replace with quiz taps.

3. Value Before Ask

Users should experience the core product value before seeing a paywall. The product is the pitch.

4. Every Screen Must Earn Its Place

If removing a screen doesn't reduce conversion, it shouldn't exist. 50% of users drop off before reaching the paywall. Every unnecessary screen kills conversion.

5. Personalization = Investment

Each quiz answer the user gives increases their sunk cost. By screen 4, they've invested time and choices — walking away feels like losing that investment. This is commitment bias.

The 8-Screen Framework

Screen 1 — Hook (3 seconds to win or lose)

  • Benefit headline, not feature description
  • "Record yourself. See how you really sound." NOT "AI-powered speech analysis tool"
  • For fresh apps: NO fake social proof, NO star ratings, NO user counts
  • Single CTA: "Try It Free"
  • Zero visual clutter

Screen 2-3 — Personalization Quiz (interactive, 1 tap each)

  • Button-based selection, never text input
  • 3-5 pre-defined options per screen
  • Each answer MUST change the experience downstream
  • If a question doesn't change anything, remove it
  • Progress indicator visible (builds completion motivation — Zeigarnik effect)

Screen 4 — Core Action (THE critical screen)

  • User DOES the main thing — record, create, try
  • This should happen within 15-20 seconds of opening the app
  • No explanation needed. Minimal text. Big CTA.
  • This is the highest-commitment moment — they've invested their voice/data/time

Screen 5 — Processing (real, not fake)

  • If real: show genuine progress with fun facts
  • If fake: users detect it — kills trust. Only show if work is happening
  • Fun facts/tips during wait reduce perceived wait time by 40%
  • Max 20-30 seconds. Beyond that, consider background processing with push notification

Screen 6 — The Reveal (Aha Moment)

  • This is the MOST important screen. The user sees personalized results for the first time
  • Show specific data from THEIR input — scores, corrections, insights
  • This screen converts more than any marketing copy ever could
  • The emotional peak: "wow, I didn't know that about myself"
  • RATING PROMPT: consider triggering SKStoreReviewController here (not on first session — on 2nd or 3rd)

Screen 7 — Value Recap (personalized bridge to paywall)

  • Every bullet references THEIR specific results
  • "Fix YOUR 11 filler words" not "Fix filler words"
  • Show what happens next: their first drill, their improvement plan
  • This screen bridges emotion (reveal) to action (subscribe)

Screen 8 — Paywall

  • See /paywall skill for detailed paywall design
  • Must feel like natural next step, not a wall

Drop-Off Prevention

ScreenExpected Drop-OffHow to Fix
Screen 1 → 215-20%Stronger hook, faster load
Quiz screens5-10% per screenFewer screens, bigger taps
Before recording10-15%Reassure: "just 30 seconds"
During processing5%Fun facts, progress bar
Reveal → Paywall10%Stronger personalized recap
Paywall70-85% dismissSee /paywall skill

Target: 50-60% of installs reach the paywall. 15-25% start trial.

Fresh App Considerations (No Social Proof)

When launching with zero ratings and zero users:

  • Do NOT add fake testimonials or star ratings
  • Do NOT say "trusted by X users" or "4.9 stars"
  • DO let the product speak: the personalized analysis is more convincing than any review
  • DO add social proof AFTER you have real reviews (10+ ratings)
  • The analysis reveal screen IS your proof — it shows the product works on THEIR data

App Store Rating Strategy

Apple allows 3 rating prompts per 365 days. Use them wisely:

TriggerWhenWhy It Works
After subscribingImmediately post-paymentHighest satisfaction — they chose to pay
After first successDrill passed at 7+/10They succeeded at something
After improvementRe-record shows higher scoresThey saw measurable growth

NEVER during onboarding. NEVER on first session. Only after demonstrated value.

Metrics to Track

  • Install → Screen 2 (hook effectiveness)
  • Screen 2 → Recording started (quiz engagement)
  • Recording → Results seen (completion rate)
  • Results → Paywall viewed (value perception)
  • Paywall → Trial started (paywall conversion)
  • Trial → Paid (product-market fit)

Anti-Patterns

PatternWhy It Fails
Feature tour carousel (3+ screens)Users skip/ignore. Zero engagement.
"How it works" explainerThey'll figure it out by doing
Fake loading/building screenUsers detect fakery — kills trust
Sign up before valueHighest-churn screen. Delay registration.
Permission requests during onboardingAsk when needed, not upfront
Text paragraphs on any screenNobody reads. Use 5-7 word headlines.
Generic paywall copyMust reference their specific results

Reference

  • conversion-data.md — Industry benchmarks and conversion rates
  • psychology.md — Psychological triggers at each step

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.