Paywall Upgrade Cro
In-app paywall and upgrade screen optimization covering feature gate design, usage...
Install
npx skills add borghei/Claude-Skills --skill paywall-upgrade-cro -g -a claude-code -y- Repository
- borghei/Claude-Skills1k
- Category
- Design
- Updated
- 12d ago
- License
- MIT + Commons Clause
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
In-app paywall and upgrade screen optimization covering feature gate design, usage limit UX, trial expiration flows, upgrade trigger timing, save offer strategy, and ethical monetization patterns.
Paywall & Upgrade Screen CRO
Production-grade framework for in-product upgrade flows. Covers feature gate design, usage limit UX, trial expiration sequences, upgrade trigger timing, dark pattern avoidance, and ethical monetization. Distinct from public pricing pages (use page-cro for those) -- this focuses on in-product moments where users have already experienced value.
Table of Contents
- Initial Assessment
- The Value-First Principle
- Paywall Trigger Architecture
- Paywall Screen Design
- Feature Gate Patterns
- Usage Limit UX
- Trial Expiration Flows
- Timing and Frequency Rules
- Upgrade Flow Optimization
- Dark Pattern Avoidance
- Platform-Specific Considerations
- Metrics and Benchmarks
- A/B Test Framework
- Output Artifacts
- Related Skills
Clarify First
Before designing the paywall, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Upgrade model: freemium-to-paid, trial-to-paid, or tier upgrade (determines the paywall type and trigger architecture).
- Free vs paid boundary: what is gated (defines the value gap the paywall communicates).
- Aha moment: so triggers fire only after value is experienced (the value-first principle).
- Platform: web, iOS, or Android (IAP rules and commissions constrain web vs app flows).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
