conversion-patterns

What this skill actually is

Every rule in data/conversion-rules.json is a real, published result — but each one is a single case study from one company, on one audience, at one funnel stage. None of them are controlled multi-trial findings, and the source only publishes winners, never the losing variants. Several of the rules in this file directly contradict each other (require a credit card vs. remove all friction; gate the paywall immediately vs. let users taste the product first) because they assume opposite starting conditions, not because one is right and one is wrong.

This skill's job is not to hand you a lever. It's to force you to name your condition before you're allowed to pick one. If you skip the condition-check and just grab the highest-lift rule, you're using this skill wrong.

When this skill triggers

Use this skill whenever a ticket touches: paywalls, trial structure or length, checkout flow, cart abandonment, upsell/upgrade prompts, streaks or habit loops, referral flows, or pricing-page/CTA display. If the ticket is about onboarding sequencing instead, that's onboarding-flow's job, not this one — check there first if you're not sure which one owns the ticket.

For pricing pages specifically, vois-patterns (PATH-F, references/pricing-pages.md) owns layout and structure. This skill owns the test-backed levers: whether to show a billing timeline, how to frame the CTA, whether to gate immediately. Use both: structure from vois-patterns, levers from here.

Mode 1: Diagnose a Ticket (new feature or screen being planned)

Before touching data/conversion-rules.json, answer these against the actual ticket: