When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see iblai-marketing-onboarding-cro. For lead capture forms (not account creation), see iblai-marketing-form-cro.
التثبيت
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see iblai-marketing-onboarding-cro. For lead capture forms (not account creation), see iblai-marketing-form-cro.
globs
null
alwaysApply
false
metadata
{"version":"1.1.0"}
/iblai-marketing-signup-flow-cro
Reduce signup friction, lift completion rates, and set users up for
successful activation.
Step 0: Context Check
Read .agents/product-marketing-context.md (or .claude/product-marketing-context.md
on older setups) first. Only ask for what isn't there.
Pin down before recommending:
Flow type
Free trial signup
Freemium account creation
Paid account creation
Waitlist / early access signup
B2B vs. B2C
Current state
Steps/screens
Required fields
Current completion rate
Where users drop off
Business constraints
Data genuinely needed at signup
Compliance requirements
What happens immediately after signup
Core Principles
1. Minimize Required Fields
Every field cuts conversion. Per field, ask:
Do we absolutely need this before they can use the product?
Can we collect this later via progressive profiling?
Can we infer this from other data?
Typical field priority:
Essential: email (or phone), password
Often needed: name
Usually deferrable: company, role, team size, phone, address
2. Show Value Before Asking for Commitment
What can you show or give before requiring signup?
Can they experience the product before creating an account?
Reverse the order: value first, signup second
3. Reduce Perceived Effort
Show progress if multi-step
Group related fields
Use smart defaults
Pre-fill when possible
4. Remove Uncertainty
Clear expectations ("Takes 30 seconds")
Show what happens after signup
No surprises (hidden requirements, unexpected steps)
Field-by-Field Optimization
Email Field
Single field (no email confirmation field)
Inline validation for format
Catch common typos (gmial.com → gmail.com)
Clear error messages
Password Field
Show-password toggle (eye icon)
Show requirements upfront, not after failure
Consider passphrase hints for strength
Update requirement indicators in real time
Better password UX:
Allow paste — don't disable
Show a strength meter instead of rigid rules
Consider passwordless options
Name Field
Single "Full name" field vs. First/Last split (test it)
Only require if immediately used (personalization)
Consider making optional
Social Auth Options
Place prominently — often higher conversion than email
