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
- BermanRoman/promt-seo-geotheir own version, first seen Nov 8, 2026
- openshift-online/rosa-boundarytheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- TserenTserenov/FMT-exocortex-templatetheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- salvo8519/fairmarktheir own version, first seen Nov 8, 2026
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.
CesarjoquinSkillpaywalls
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
CesarjoquinSkillpopups
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
coreyhaines31Skillmarketing-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
roerohanSkillprospecting
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
roerohanSkillemails
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
Other versions100 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 100
- coreyhaines31/marketingskills★ 59ksame name
- anthropics/knowledge-work-plugins★ 35ksame name
- actions/runner-images★ 14ksame name
- BuilderIO/agent-native★ 7.6ksame name
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- ColeMurray/background-agents★ 3.5ksame name
- huytieu/COG-second-brain★ 1.3ksame name
- openai/mcp-extensions★ 1.1ksame name
- Nexus-JPF/note-companion★ 874same name
- elevenlabs/skills★ 539same name
90 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository76 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/components.mdcCursor rule
- .cursor/rules/currency.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/file-structure.mdcCursor rule
- .cursor/rules/forbidden-patterns.mdcCursor rule
- .cursor/rules/mvvm-architecture.mdcCursor rule
- .cursor/rules/pricing-display.mdcCursor rule
- .cursor/rules/scope.mdcCursor rule
- .cursor/rules/swift-conventions.mdcCursor rule
- accessibilitySkill
- animationsSkill
- apple-developer-authSkill
- apple-signinSkill
- app-store-preflightSkill
- asc-app-create-uiSkill
- asc-aso-auditSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-metadata-yamlSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-screenshot-resizeSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- ascSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-whats-new-writerSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- billing-finance-calculatorSkill
- buildSkill
- business-modelSkill
- chartsSkill
- consolidate-errorsSkill
- content-composerSkill
- crashSkill
- debuggingSkill
- feature-directory-structureSkill
- feedback-statesSkill
- fix-errorSkill
- formsSkill
- foundation-modelsSkill
- hapticsSkill
- healthkitSkill
- layoutSkill
- listsSkill
- navigationSkill
- notificationsSkill
- onboarding-questionnaireSkill
- The first 60 shown.
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
- Distinctive: line 22
If removing a screen doesn't reduce conversion, it shouldn't exist.
- Distinctive: line 40
If a question doesn't change anything, remove it
- Distinctive: line 46
No explanation needed. Minimal text.
- Distinctive: line 50
If real: show genuine progress with fun facts
- Distinctive: line 51
If fake: users detect it — kills trust.
- Distinctive: line 63
Every bullet references THEIR specific results
- Distinctive: line 70
Must feel like natural next step, not a wall
- Distinctive: line 87
When launching with zero ratings and zero users:
- Distinctive: line 88
Do NOT add fake testimonials or star ratings
- Distinctive: line 89
Do NOT say "trusted by X users" or "4.9 stars"
- Distinctive: line 90
DO let the product speak: the personalized analysis is more convincing than any review
- Distinctive: line 91
DO add social proof AFTER you have real reviews (10+ ratings)
- Distinctive: line 104
NEVER during onboarding. NEVER on first session.
“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.
Files
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
| Screen | Expected Drop-Off | How to Fix |
| Screen 1 → 2 | 15-20% | Stronger hook, faster load |
| Quiz screens | 5-10% per screen | Fewer screens, bigger taps |
| Before recording | 10-15% | Reassure: "just 30 seconds" |
| During processing | 5% | Fun facts, progress bar |
| Reveal → Paywall | 10% | Stronger personalized recap |
| Paywall | 70-85% dismiss | See /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:
| Trigger | When | Why It Works |
| After subscribing | Immediately post-payment | Highest satisfaction — they chose to pay |
| After first success | Drill passed at 7+/10 | They succeeded at something |
| After improvement | Re-record shows higher scores | They 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
| Pattern | Why It Fails |
| Feature tour carousel (3+ screens) | Users skip/ignore. Zero engagement. |
| "How it works" explainer | They'll figure it out by doing |
| Fake loading/building screen | Users detect fakery — kills trust |
| Sign up before value | Highest-churn screen. Delay registration. |
| Permission requests during onboarding | Ask when needed, not upfront |
| Text paragraphs on any screen | Nobody reads. Use 5-7 word headlines. |
| Generic paywall copy | Must reference their specific results |
Reference
- conversion-data.md — Industry benchmarks and conversion rates
- psychology.md — Psychological triggers at each step
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
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.

