Get the FREE Ultimate OpenClaw Setup Guide →

form-optimization

Scanned
npx machina-cli add skill Dragoon0x/Product-Skills/form-optimization --openclaw
Files (1)
SKILL.md
1.7 KB

Form Optimization

Reduce abandonment in every form, signup, and checkout flow.

How to use

  • /form-optimization Apply 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")

Source

git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/conversion/form-optimization/SKILL.mdView on GitHub

Overview

Form optimization reduces friction in signup, checkout, and multi-field inputs by enforcing field justification, minimal initial data, and clear progression. It leverages multi-step flows, inline validation, and completion-focused micro-copy to improve conversions. Labels above fields, contextual help, and outcome-descriptive buttons guide users to completion.

How This Skill Works

Apply the constraints to your form: justify every field and remove unnecessary ones; for forms with 5+ fields, split into steps with a visible Step X of N indicator and save progress. Implement real-time inline validation with actionable error messages and positive green checks for valid fields, plus upfront password/requirements visibility. Finish with a confirmation that clearly states what happens after submission.

When to Use It

  • Building signup flows that should collect only essential information up front
  • Checkout pages where reducing friction lowers abandoned carts
  • Any multi-field input form that contains 5 or more fields
  • Onboarding flows that gather additional data later after initial signup
  • Long application forms where inline validation and clear micro-copy improve submission rates

Quick Start

  1. Step 1: Audit each field and justify its necessity; remove anything not clearly required
  2. Step 2: If 5+ fields exist, split into steps, add a progress indicator, and ensure progress is saved on back/forward
  3. Step 3: Add inline validation, descriptive error messages, and completion micro-copy; adjust button text to reflect the outcome

Best Practices

  • Justify every field and remove anything that isn’t immediately necessary
  • Break 5+ fields into steps with a clear progress indicator (Step 2 of 3, etc.) and save progress
  • Validate inline as users complete each field; provide error messages that state what’s wrong and how to fix it
  • Never clear the form on submission errors; preserve user input
  • Use clear micro-copy: labels above fields, helpful text below, and outcome-descriptive button text like 'Create account' or 'Complete order'; show a final confirmation after submission

Example Use Cases

  • A 3-step signup flow that collects only email and password upfront, with optional profile details on a follow-up screen
  • A checkout process that splits 6+ fields into steps with a Step 1 of 3 progress bar and real-time validation
  • An onboarding form where essential data is gathered first and advanced details collected later in a guided flow
  • A loan application that groups related fields into steps, with inline validation and explicit error remediation
  • A support/contact form that validates email/phone in real-time and shows what will happen after submission

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers