← ClaudeAtlas

cro-formslisted

Optimizes forms for lead generation, signups, and data collection with friction reduction, field optimization, validation UX, and progressive profiling strategies. Use when user asks about form optimization, form fields, lead form, signup form, form completion, progressive profiling, form UX, 폼 최적화, 양식, or 리드 폼.
Yoodaddy0311/artibot · ★ 3 · AI & Automation · score 65
Install: claude install-skill Yoodaddy0311/artibot
# CRO - Form Optimization ## When This Skill Applies - Optimizing lead generation and signup forms - Reducing form field count and friction - Improving form validation and error handling UX - Designing progressive profiling strategies - Analyzing form abandonment and completion rates ## Core Guidance ### 1. Form Optimization Process ``` Audit Current Form -> Analyze Abandonment -> Identify Friction -> Reduce Fields -> Improve UX -> Test Changes -> Validate -> Iterate ``` ### 2. Field Count Impact | Fields | Avg Completion Rate | Recommendation | |--------|-------------------|---------------| | 1-3 | 25-30% | Best for top-of-funnel, signups | | 4-5 | 20-25% | Good for lead gen with qualification | | 6-7 | 15-20% | Acceptable for high-intent (demo, quote) | | 8-10 | 10-15% | Only for high-value offers | | 10+ | <10% | Avoid; use progressive profiling | **Rule**: Every field removed can increase conversions 5-10%. ### 3. Field Necessity Audit | Question | If Yes | If No | |----------|--------|-------| | Is it needed to fulfill the request? | Keep | Remove | | Can it be auto-detected? | Auto-fill | Remove field | | Can it be asked later? | Progressive profile | Remove from form | | Is it truly needed for qualification? | Keep | Remove | | Can a smart default work? | Default + optional change | Simplify | ### 4. Field Ordering Best Practices | Position | Best Fields | Rationale | |----------|-----------|-----------| | First | Name, email (easy fields) | Build momentum |