form-optimization
Form Optimization
Reduce abandonment in every form, signup, and checkout flow.
How to use
/form-optimizationApply form optimization constraints to this conversation.
Constraints
Field Reduction
- MUST justify every field. If you can't explain why it's needed now, remove it.
- SHOULD collect the minimum at signup, gather the rest during onboarding
- Name fields: only ask if you'll use the name in the product experience
- Phone number: only ask if you'll actually call or text them
- NEVER ask for information you can infer or look up
Multi-Step Logic
- Break forms with 5+ fields into steps
- Show progress: "Step 2 of 3" with a visual indicator
- Group related fields in the same step
- MUST save progress between steps (don't lose data on back navigation)
- Final step should feel like a confirmation, not another form
Validation
- MUST validate inline (as the user completes each field, not on submit)
- Error messages MUST say what went wrong AND how to fix it
- NEVER clear the form on submission error
- SHOULD use positive confirmation (green checkmark) for valid fields
- Password requirements: show them before the user types, not after they fail
Micro-Copy
- Labels above fields, not inside (placeholders disappear and confuse)
- Help text below fields for anything non-obvious
- Button text should describe the outcome: "Create account" not "Submit"
- MUST show what happens after submission ("We'll email you a confirmation")
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1