conversion-flow-cro

Name: conversion-flow-cro
Author: MoizIbnYousaf

27stars5forks

How to install conversion-flow-cro?

moizibnyousaf/marketing-cli/conversion-flow-cro

$npx -y skills add MoizIbnYousaf/marketing-cli --skill conversion-flow-cro

Installs into the current project.

Summary

Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specific copy/UX changes with A/B test plans. Use when someone says 'signup flow', 'onboarding optimization', 'checko

Files · 1

View on GitHub

SKILL.md

1	# Conversion Flow CRO
2
3	## Purpose
4
5	Audit and optimize any multi-step conversion flow — signup, onboarding, trial-to-paid, checkout, upgrade. Map every step, find where people drop off, and fix each screen with specific copy and UX changes.
6
7	## Reads
8
9	- `brand/audience.md` — Personas, pain points, motivation levels at each stage
10	- `brand/positioning.md` — Value props for reinforcement copy at each step
11	- `brand/voice-profile.md` — Brand voice for all copy suggestions
12
13	## Brand Integration
14
15	- audience.md — Persona determines friction tolerance. A developer persona accepts more setup steps; a non-technical buyer needs fewer. Pain points inform which value reminders to show at each step.
16	- positioning.md — Value proposition reinforcement copy at each step should echo the positioning angle. If the brand positions on "saves time," every motivation booster references time savings.
17	- voice-profile.md — All redesigned copy (headlines, CTAs, supporting text) must match brand voice. A casual brand writes "Almost there!" while a professional brand writes "One final step."
18
19	## Workflow
20
21	### Step 1: Map the Current Flow
22
23	Get the flow information. Try these in order:
24	1. User provides screenshots or screen recordings — Best source, map directly
25	2. Read the codebase — If accessible, find route files, page components, and form definitions
26	3. User walks through the flow verbally — Accept but flag that recommendations will be more accurate with actual screens
27	4. Use browser tool on live URL — Walk through the flow step by step
28
29	If the flow is partially provided (only some screens), audit what's available and note which steps need investigation.
30
31	Document every screen/step in the flow:
32
33	```
34	Flow: [Signup / Onboarding / Upgrade / Checkout]
35
36	Step 1: [Page/Screen name]
37	- URL/Route: [path]
38	- Fields/Actions: [what user must do]
39	- Copy: [headline, body, CTA]
40	- Friction points: [identified issues]
41
42	Step 2: [Next screen]
43	...
44
45	Total steps: [N]
46	Total required fields: [N]
47	Total decisions: [N]
48	Estimated completion time: [X minutes]
49	```
50
51	### Step 2: Identify Drop-Off Points
52
53	For each step, assess drop-off risk:
54
55	\| Risk Factor \| Score 1-5 \| Notes \|
56	\|------------\|-----------\|-------\|
57	\| Too many fields \| \| More than 3 per step = high risk \|
58	\| Unclear value \| \| User doesn't know why this step matters \|
59	\| Unexpected ask \| \| Requesting info that feels premature \|
60	\| No progress signal \| \| User doesn't know how far along they are \|
61	\| Decision fatigue \| \| Too many choices without guidance \|
62	\| Trust gap \| \| Asking for sensitive info without context \|
63	\| Technical friction \| \| Slow load, validation errors, mobile issues \|
64
65	### Step 3: Apply Friction Reduction
66
67	For each step, apply these principles:
68
69	#### Progressive Disclosure
70	- Ask for minimum info at each step
71	- Defer optional fields to later (post-signup settings)
72	- Start with the easiest, most natural question
73	- Example: Email only -> Name -> Company -> Role (not all at once)
74
75	#### Single-Field Starts
76	- First interaction should be ONE field or ONE click
77	- "Enter your email to get started" > 5-field signup form
78	- Google/GitHub OAuth as primary option, email form as secondary
79
80	#### Smart Defaults
81	- Pre-select the most common option
82	- Use detection (timezone, language, company size from email domain)
83	- Show recommended plan with visual emphasis
84
85	#### Motivation Maintenance
86	- Show progress (Step 2 of 4)
87	- Remind of value at each step ("You're 1 step away from [outcome]")
88	- Use micro-commitments (each step delivers a small win)
89	- Show social proof inline ("12,000 teams completed this step today")
90
91	#### Social Proof Injection Points
92	- Before payment: "Join [X] companies already using [Product]"
93	- During onboarding: "[Role] at [Company] set this up in 3 minutes"
94	- At upgrade prompt: "[X]% of free users upgrade within [Y] days"
95
96	#### Urgency Without Sleaze
97	- Real deadlines: "Trial ends in 7 days" (if true)
98	- Opportunity cost: "Teams using [feature] save [X] hours/week"
99	- Progress anchoring: "You've already set up [X] — unlock [Y] to get full value"
100	- Never: fake countdown timers, "only 2

People who liked this also viewed

6 picks

Type

conversion-flow-cro

27stars5forks

View on GitHub

How to install conversion-flow-cro?

moizibnyousaf/marketing-cli/conversion-flow-cro

$npx -y skills add MoizIbnYousaf/marketing-cli --skill conversion-flow-cro

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Conversion Flow CRO
2
3	## Purpose
4
5	Audit and optimize any multi-step conversion flow — signup, onboarding, trial-to-paid, checkout, upgrade. Map every step, find where people drop off, and fix each screen with specific copy and UX changes.
6
7	## Reads
8
9	- `brand/audience.md` — Personas, pain points, motivation levels at each stage
10	- `brand/positioning.md` — Value props for reinforcement copy at each step
11	- `brand/voice-profile.md` — Brand voice for all copy suggestions
12
13	## Brand Integration
14
15	- audience.md — Persona determines friction tolerance. A developer persona accepts more setup steps; a non-technical buyer needs fewer. Pain points inform which value reminders to show at each step.
16	- positioning.md — Value proposition reinforcement copy at each step should echo the positioning angle. If the brand positions on "saves time," every motivation booster references time savings.
17	- voice-profile.md — All redesigned copy (headlines, CTAs, supporting text) must match brand voice. A casual brand writes "Almost there!" while a professional brand writes "One final step."
18
19	## Workflow
20
21	### Step 1: Map the Current Flow
22
23	Get the flow information. Try these in order:
24	1. User provides screenshots or screen recordings — Best source, map directly
25	2. Read the codebase — If accessible, find route files, page components, and form definitions
26	3. User walks through the flow verbally — Accept but flag that recommendations will be more accurate with actual screens
27	4. Use browser tool on live URL — Walk through the flow step by step
28
29	If the flow is partially provided (only some screens), audit what's available and note which steps need investigation.
30
31	Document every screen/step in the flow:
32
33	```
34	Flow: [Signup / Onboarding / Upgrade / Checkout]
35
36	Step 1: [Page/Screen name]
37	- URL/Route: [path]
38	- Fields/Actions: [what user must do]
39	- Copy: [headline, body, CTA]
40	- Friction points: [identified issues]
41
42	Step 2: [Next screen]
43	...
44
45	Total steps: [N]
46	Total required fields: [N]
47	Total decisions: [N]
48	Estimated completion time: [X minutes]
49	```
50
51	### Step 2: Identify Drop-Off Points
52
53	For each step, assess drop-off risk:
54
55	\| Risk Factor \| Score 1-5 \| Notes \|
56	\|------------\|-----------\|-------\|
57	\| Too many fields \| \| More than 3 per step = high risk \|
58	\| Unclear value \| \| User doesn't know why this step matters \|
59	\| Unexpected ask \| \| Requesting info that feels premature \|
60	\| No progress signal \| \| User doesn't know how far along they are \|
61	\| Decision fatigue \| \| Too many choices without guidance \|
62	\| Trust gap \| \| Asking for sensitive info without context \|
63	\| Technical friction \| \| Slow load, validation errors, mobile issues \|
64
65	### Step 3: Apply Friction Reduction
66
67	For each step, apply these principles:
68
69	#### Progressive Disclosure
70	- Ask for minimum info at each step
71	- Defer optional fields to later (post-signup settings)
72	- Start with the easiest, most natural question
73	- Example: Email only -> Name -> Company -> Role (not all at once)
74
75	#### Single-Field Starts
76	- First interaction should be ONE field or ONE click
77	- "Enter your email to get started" > 5-field signup form
78	- Google/GitHub OAuth as primary option, email form as secondary
79
80	#### Smart Defaults
81	- Pre-select the most common option
82	- Use detection (timezone, language, company size from email domain)
83	- Show recommended plan with visual emphasis
84
85	#### Motivation Maintenance
86	- Show progress (Step 2 of 4)
87	- Remind of value at each step ("You're 1 step away from [outcome]")
88	- Use micro-commitments (each step delivers a small win)
89	- Show social proof inline ("12,000 teams completed this step today")
90
91	#### Social Proof Injection Points
92	- Before payment: "Join [X] companies already using [Product]"
93	- During onboarding: "[Role] at [Company] set this up in 3 minutes"
94	- At upgrade prompt: "[X]% of free users upgrade within [Y] days"
95
96	#### Urgency Without Sleaze
97	- Real deadlines: "Trial ends in 7 days" (if true)
98	- Opportunity cost: "Teams using [feature] save [X] hours/week"
99	- Progress anchoring: "You've already set up [X] — unlock [Y] to get full value"
100	- Never: fake countdown timers, "only 2

People who liked this also viewed

6 picks

Type