Your free users hit the paywall. Why do they close it?
Paste the upgrade screen your free or trial users see - a feature gate, a usage-limit wall, a trial-expired page, an upsell modal - exactly as they see it, with the buttons in [brackets], and a few lines on what triggers it. Your browser finds which of the seven paywall components are missing, flags dark patterns (guilt-trip decline copy, a hidden close, fake urgency) and conversion killers (asking before value, showing it every session), checks the annual saving you state against your prices and reads your funnel. Free, before you sign in, and nothing is uploaded. Then the audit gives the fixes in order, and the redesign writes the new screen, when and how often to show it, and the tests to run.
The products and numbers in the examples are invented. Three are audits (the project-limit one also carries its redesign, one click after the audit) and one is a redesign; each comes with a saved model reply, so you can see the whole page without signing in or spending a credit.
What this does, and what it does not
A paywall converts when it arrives after the user has had real value, shows them what they would get rather than what they hit, puts the price where they can see it, and lets them say no without a fight. Most in-app upgrade screens fail on one of those: a bare "You've reached your limit" with a lone "Upgrade" button, a trial that ends without a word of warning, a modal on the first launch, a close button that fades in after five seconds, "No thanks, I don't want to get fit". This page reads your screen for the seven components the skill names, every button and what it says, the prices and whether "save 25%" is true, and your context for when and how often it fires - and flags each mistake with the line that shows it.
The paid lanes see your screen (the middle is cut past 6,000 characters, and the page says so), your context (past 4,000) and the page's scan. Your input stays in this browser unless you run a lane. Every reply is held to your input: quotes are checked word for word, and no price, rate or social-proof count may be invented - the redesign writes [placeholders] for what only you know. This is for in-app moments; a public pricing page is page CRO, and the run will say so. Derived from the agent skill @coreyhaines31/paywall-upgrade-cro, published in its current form as @coreyhaines31/paywalls, by Corey Haines (coreyhaines31/marketingskills, MIT): its four principles, trigger points, the seven screen components, the feature-lock, usage-limit and trial-expiration templates, the timing and frequency rules, the anti-patterns and the experiment library. Sources are listed in llms.txt.