# Form Cro

Form optimization for lead capture, contact, demo request, application, and checkout...

- Repository: https://github.com/borghei/Claude-Skills (1026 stars)
- Category: Design
- License: MIT + Commons Clause
- Last updated: 2026-10-23
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add borghei/Claude-Skills --skill form-cro -g -a claude-code -y`
Codex: `npx skills add borghei/Claude-Skills --skill form-cro -g -a codex -y`
Cursor: `npx skills add borghei/Claude-Skills --skill form-cro -g -a cursor -y`
Gemini CLI: `npx skills add borghei/Claude-Skills --skill form-cro -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add borghei/Claude-Skills`

## Description

Form optimization for lead capture, contact, demo request, application, and checkout forms. Covers field-cost analysis, multi-step form design, validation UX, mobile optimization, and A/B testing frameworks.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Form CRO

Production-grade form optimization framework covering field-cost analysis, layout engineering, multi-step form architecture, validation UX patterns, mobile-specific optimization, and structured A/B test design. Applicable to lead capture, contact, demo request, application, survey, and checkout forms. For signup/registration flows, use signup-flow-cro.

---

## Table of Contents

- [Initial Assessment](#initial-assessment)
- [Field-Cost Analysis Framework](#field-cost-analysis-framework)
- [Multi-Step vs Single-Step Decision](#multi-step-vs-single-step-decision)
- [Field Design Patterns](#field-design-patterns)
- [Validation UX](#validation-ux)
- [CTA and Submit Button Optimization](#cta-and-submit-button-optimization)
- [Mobile Form Optimization](#mobile-form-optimization)
- [Trust and Context Elements](#trust-and-context-elements)
- [Form Type Playbooks](#form-type-playbooks)
- [A/B Test Framework](#ab-test-framework)
- [Metrics and Measurement](#metrics-and-measurement)
- [Output Artifacts](#output-artifacts)
- [Related Skills](#related-skills)

---

## Clarify First

Before optimizing the form, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

- **Form type:** lead capture, contact, demo, application, or checkout (sets the optimal field count and playbook).
- **Current fields + which are used in follow-up:** reveals which fields to cut or enrich (the core of field-cost analysis).
- **Current completion rate + where users abandon:** baseline and the specific friction point to target.
- **Compliance requirements:** GDPR/HIPAA fields that cannot be removed (constrains the field reduction).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

## Initial Assessment

### Required Context

The rest: https://github.com/borghei/Claude-Skills/blob/HEAD/business-growth/form-cro/SKILL.md