When the user wants to optimize any form that is NOT signup/registration — lead capture, contact, demo request, application, survey, or checkout forms; "form friction," "form completion rate," "form abandonment," "too many fields," "nobody fills out our form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Maximize form completion rates while capturing the data that matters.
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Before recommending, identify:
Each field reduces completion. Rule of thumb: 3 fields = baseline; 4-6 fields = 10-25% reduction; 7+ fields = 25-50%+ reduction. For each field ask: Is it absolutely necessary before we can help them? Can we get it another way? Can we ask later?
Clear value proposition above the form; make what they get obvious; reduce perceived effort (field count, labels).
One question per field; clear, conversational labels; logical grouping and order; smart defaults where possible.
Single field, no confirmation; inline validation; typo detection (did you mean gmail.com?); proper mobile keyboard.
Test single "Name" vs. First/Last — single field reduces friction; split only if personalization requires it.
Make optional if possible; if required, explain why; auto-format as they type; handle country codes.
Auto-suggest for faster entry; enrich after submission (Clearbit, etc.); consider inferring from email domain.
Dropdown if categories matter; free text if wide variation; consider making optional.
Optional; reasonable character guidance; expand on focus.
"Select one..." placeholder; searchable if many options; radio buttons if < 5 options; "Other" option with text field.
Clear, parallel labels; reasonable option count; consider "Select all that apply" instruction.
Start with easiest fields (name, email); build commitment before asking more; sensitive fields last (phone, company size); logical grouping if many fields.
Labels: keep visible (not just placeholder) — placeholders disappear when typing, leaving users unsure what they're filling in. Placeholders: examples, not labels. Help text: only when genuinely helpful.
Good:
Email
[name@company.com]
Bad:
[Enter your email address] ← Disappears on focus
Sufficient spacing between fields; clear visual hierarchy; CTA button stands out; mobile-friendly tap targets (44px+).
Single column: higher completion, mobile-friendly. Multi-column: only for short related fields (First/Last name). When in doubt, single column.
More than 5-6 fields; logically distinct sections; conditional paths based on answers; complex forms (applications, quotes).
Progress indicator (step X of Y); start easy, end with sensitive; one topic per step; allow back navigation; save progress (don't lose data on refresh); clear indication of required vs. optional.
Validate as they move to the next field, not aggressively while typing; clear visual indicators (green check, red border).
Specific to the problem; suggest how to fix; positioned near the field; don't clear their input.
Good: "Please enter a valid email address (e.g., name@company.com)" Bad: "Invalid input"
Focus on first error field; summarize errors if multiple; preserve all entered data; don't clear the form on error.
Weak: "Submit" | "Send" Strong: "[Action] + [What they get]" — "Get My Free Quote," "Download the Guide," "Request Demo," "Send Message," "Start Free Trial"
Immediately after last field; left-aligned with fields; sufficient size and contrast; mobile: sticky or clearly visible.
Loading (disable button, show spinner); success confirmation (clear next steps); error handling (clear message, focus on issue).
Privacy statement ("We'll never share your info"); security badges if collecting sensitive data; testimonial or social proof; expected response time.
"Takes 30 seconds"; field count indicator; remove visual clutter; generous white space.
"No spam, unsubscribe anytime" · "We won't share your number" · "No credit card required"
Minimum viable fields (often just email); clear value proposition for what they get; consider enrichment questions post-download; test email-only vs. email + name.
Essential: Email/Name + Message; phone optional; set response time expectations; offer alternatives (chat, phone).
Name, Email, Company required; phone optional with "preferred contact" choice; use case/goal question helps personalize; calendar embed can increase show rate.
Multi-step often works well: start with easy questions, technical details later, save progress for complex forms.
Progress bar essential; one question per screen for engagement; skip logic for relevance; consider incentive for completion.
Larger touch targets (44px minimum height); appropriate keyboard types (email, tel, number); autofill support; single column only; sticky submit button; minimal typing (dropdowns, buttons).
Form start rate (page views → started); completion rate (started → submitted); field drop-off (which fields lose people); error rate by field; time to complete (total and by field); mobile vs. desktop completion by device.
Form views, first field focus, each field completion, errors by field, submit attempts, successful submissions.
For each issue: Issue (what's wrong), Impact (estimated effect on conversions), Fix (specific recommendation), Priority (High/Medium/Low).
Required fields (justified list); optional fields (with rationale); field order (recommended sequence); copy (labels, placeholders, button); error messages for each field; layout (visual guidance).
Ideas to A/B test with expected outcomes
Layout & Flow — single-step vs. multi-step with progress bar; 1-column vs. 2-column layout; embedded on page vs. separate page; vertical vs. horizontal field alignment; form above fold vs. after content.
Field Optimization — reduce to minimum viable fields; add/remove phone number field; add/remove company/organization field; required vs. optional field balance; field enrichment to auto-fill known data; hide fields for returning/known visitors.
Smart Forms — real-time validation for emails and phone numbers; progressive profiling (ask more over time); conditional fields based on earlier answers; auto-suggest for company names.
Labels & Microcopy — field label clarity and length; placeholder text; help text show vs. hide vs. on-hover; error message tone (friendly vs. direct).
CTAs & Buttons — button text ("Submit" vs. "Get My Quote" vs. specific action); color and size; placement relative to fields.
Trust Elements — privacy assurance near form; trust badges next to submit; testimonial near form; expected response time display.
Demo Request — with/without phone requirement; "preferred contact method" choice; "What's your biggest challenge?" question; calendar embed vs. form submission.
Lead Capture — email-only vs. email + name; value proposition messaging above form; gated vs. ungated content; post-submission enrichment questions.
Contact — department/topic routing dropdown; with/without message field requirement; alternative contact methods (chat, phone); expected response time messaging.
Larger touch targets; keyboard types by field; sticky submit button; auto-focus first field on page load; form container styling (card vs. minimal).
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.