paywalls helps an agent decide when and how to ask free users to pay. It sets four principles, value before the ask, showing the value, a friction-free path and respect for a no, and then lays out trigger points and screen components.
Two references hold experiment ideas and guidance for consumer iOS and Android subscription apps.
What You Get
- Guidance on four trigger points: feature gates, usage limits, trial expiration and time-based prompts
- A seven-part paywall screen layout from headline to escape hatch
- Text mockups for feature lock, usage limit and trial expiration paywalls
- Timing and frequency rules, including when not to show a paywall
- A test plan with metrics, plus a reference for mobile subscription paywalls
Common Use Cases
- Designing the screen shown when a free user hits a limit
- Planning trial expiry warnings at seven, three and one day
- Deciding how often to show an upgrade prompt after a dismissal
- Reviewing a paywall for dark patterns
- Setting up a paywall inside the onboarding of a subscription app
What Makes It Unique
It ties every paywall to a value moment and requires a visible way back, with cool-downs measured in days. It lists dark patterns to avoid, including hidden close buttons and fake countdowns, and it separates in-app upgrade screens from public pricing pages, which belong to other skills.
Under The Hood
The SKILL.md and two references are loaded as context. It ships no scripts and runs no commands. The agent reads the product marketing context file in your project when it exists. It reaches no services and writes no files. Output is written recommendations and text mockups of paywall screens.