paywalls

Designs and optimizes in-app paywalls, upgrade screens, and feature gates for freemium conversion.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill paywalls-nicolaerotaru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paywalls
Source: https://github.com/NicolaeRotaru/ad-mycity/tree/main/.cursor/skills/paywalls
Command: npx skills add https://github.com/NicolaeRotaru/ad-mycity --skill paywalls-nicolaerotaru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Free users often never convert because upgrade prompts appear at the wrong moment, hide the value of paid features, or create friction that erodes trust. This Skill provides structured guidance for designing in-app paywalls and upgrade flows that convert users after they have experienced real value. ## Core Features & Use Cases - Paywall Trigger Design: Defines when to show upgrade prompts (feature gates, usage limits, trial expiration, time-based) and when not to, with frequency and cool-down rules. - Screen Component Blueprints: Provides ready-made layouts for feature-lock, usage-limit, and trial-expiration paywalls, covering headline, value demonstration, pricing, social proof, CTA, and escape hatch. - A/B Testing & Metrics: Lists what to test (timing, copy, pricing presentation) and which metrics to track (impression rate, click-through, completion, revenue per user). - Use Case: A marketplace app wants to convert free shop owners to a paid tier. Use this Skill to design a usage-limit paywall that shows what upgrading unlocks, respects the "no", and includes an experiment plan. ## Quick Start Ask the assistant to design an upgrade screen for users who hit the free plan limit, including headline, feature comparison, pricing, and a dismiss option.

Frequently Asked Questions about paywalls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a paywall that converts free users to paid?▼

Show the paywall only after the user has experienced real value, demonstrate what the paid features do rather than just describing them, and keep the upgrade path friction-free. Always include a clear escape hatch like "Not now" to preserve trust for future conversion.

When should an upgrade prompt appear in an app?▼

Trigger prompts after an aha moment, when a user clicks a paid-only feature, hits a genuine usage limit, or nears trial expiration. Avoid showing prompts during onboarding, mid-flow, or repeatedly after dismissal, and enforce cool-down periods of days rather than hours.

What components should a paywall screen include?▼

A paywall screen needs a benefit-focused headline, a value demonstration or preview, a feature comparison with the current plan marked, clear pricing, social proof, a specific value-oriented CTA, and a visible escape hatch to continue on the free plan.

What metrics should I track for paywall A/B tests?▼

Track paywall impression rate, click-through to upgrade, checkout completion rate, revenue per user, and post-upgrade churn. Test variables include trigger timing, headline copy, price presentation, trial length, feature emphasis, and layout.

What paywall dark patterns should be avoided?▼

Avoid hiding the close button, confusing plan selection, guilt-trip copy, asking before value is delivered, overly frequent prompts, blocking critical flows, and complicated upgrade processes. These patterns damage trust and increase churn.