A paywall that converts once and churns is a loss booked late.
The upgrade prompt fires after the user has felt the value, not before, and that timing is the whole design. Paywall screens, feature gates, trial-expiry states, and usage-limit prompts each get a trigger, a message structure, a plan presentation, and an experiment to prove the moment was right. Public pricing pages are suede-site-alchemy; tier architecture is suede-pricing; cancel and save flows are suede-churn-prevention.
View skill folder Install options
When to reach for it
The user wants to build or improve an in-product upgrade screen, feature gate, or trial-expiration prompt.
What's inside
- Initial Assessment
- Core Principles
- Paywall Trigger Points
- Paywall Screen Components
- Specific Paywall Types
- Timing and Frequency
- Upgrade Flow Optimization
- A/B Testing
- Anti-Patterns to Avoid
- Task-Specific Questions
- Related Skills
Example prompt
Use $suede-paywalls on [target]. The user wants to build or improve an in-product upgrade screen, feature gate, or trial-expiration prompt. Work through paywall screens, feature gates, trial-expiry states, and free-to-paid prompts, ground every recommendation in evidence the user can check, and return the decisions, the reasoning, and what to measure next.Reference material
Loaded on demand, not up front:
Credit
This Suede skill includes licensed source material. Attribution and licence terms remain in NOTICE.md.
Install this skill
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.
$ /plugin marketplace add JasonColapietro/suede-creator-skills $ /plugin install suede-skills@suede
$ codex plugin add suede-skills@suede-codex
Cursor, Copilot, and Windsurf install through the skills CLI. Every path is on the install page, and every folder is readable first on GitHub.