Skip to main content
skill CX Codex

form-strategy — Claude Code skill: form design, validation

form-strategy — a skill for building forms that convert and keep spam out. Guides you through field strategy, validation rules, bot detection, and CRM integration.

MIT 312 installs ★ 1,107 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add rampstackco/claude-skills --skill form-strategy -a claude-code
Open on GitHub

What form-strategy does

form-strategy structures form work into five dimensions: field strategy (ask only what matters), field design (input types, labels above inputs), validation (clear error messages, blur-time checks), spam layers (honeypot, rate limiting, captcha if needed), and post-submit flow (confirmation, email, data persistence). The skill triggers on form design, audit, or when conversion drops and spam rises.

Inside is a step-by-step workflow: audit current forms, set success metrics per form, cut fields ruthlessly, set up spam defense, and integrate with downstream systems (CRM, email, support). Each dimension has concrete rules: labels beat placeholders, validate on blur not keystroke, honeypot stops most low-effort bots without UX friction.

Use it for contact forms, signup, checkout, multi-step flows, embedded forms. Covers both high-tech moves (optimistic UI, state persistence across steps) and pragmatic ones (how to block spam when a form goes public immediately).

What it helps with

  • decide which form fields to keep now and which to ask later
  • write validation messages that help users fix errors without abandoning the form
  • add spam defense (honeypot, rate limiting, captcha) without killing conversion
  • build a multi-step form that saves state so users don't lose data on refresh
  • wire form submissions to a CRM or email system and verify data arrives correctly

Example prompts for the agent

  • Audit my contact form — 7 fields, conversion dropped from 8% to 3%, spam is overwhelming. Which fields should I cut and how do I stop bots?
  • Design a checkout flow for my e-commerce site. What fields per step, how to validate addresses, how to keep data if the browser closes?
  • Review all forms on our site: list the fields, current conversion rates, and any validation or spam-defense gaps

How to install form-strategy

1Skills CLI (Vercel)

npx skills add rampstackco/claude-skills --skill form-strategy -a claude-code

2Manually: put the files in place

~/.claude/skills/form-strategy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/form-strategy/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about form-strategy

How do I install form-strategy in Claude Code?

Run npx skills add rampstackco/claude-skills --skill form-strategy -a claude-code, then read the guide in ~/.claude/skills/form-strategy/SKILL.md.

What does form-strategy do?

It gives a five-part method: which fields to ask for, how to design each one, when and how to validate, how to layer spam defense, and what to do after submit. Designed to raise conversion and cut spam volume.

When should I use a honeypot instead of CAPTCHA?

Honeypot is a hidden field that bots fill but humans don't. It catches low-effort spam without extra friction. Use CAPTCHA (Turnstile, hCaptcha) when honeypot and rate limits aren't enough, but be ready for a small conversion hit.

Source text

SKILL.md · MIT
---
name: form-strategy
description: "Design forms that convert, validate well, resist spam, and integrate cleanly with downstream systems. Use this skill when designing or auditing any form (contact, signup, checkout, multi-step, embedded), planning validation logic, fighting spam, choosing form tooling, or improving form conversion. Triggers on form design, form validation, form conversion, multi-step form, form spam, captcha, honeypot, form abandonment, signup form, contact form. Also triggers when form completion rates are low or spam is overwhelming."
category: cross-cutting
catalog_summary: "Form design, validation patterns, spam prevention, conversion tuning"
display_order: 1
---

# Form Strategy

Forms are where intent becomes action. Design them well or lose conversions, frustrate users, and drown in spam. Stack-agnostic.

---

## When to use

- Designing or redesigning a form
- Conversion is dropping on a key form
- Spam volume is overwhelming the inbox or database
- Auditing forms across a site
- Planning validation logic
- Choosing form tooling (form service, custom build, no-code)
- Integrating forms with CRM, email, or other downstream systems
- Multi-step form decisions

## When NOT to use

- Generic conversion optimization (use `cro-optimization`)
- The copy on the form (use `landing-page-copy`)
- Backend handling beyond form-specific concerns (use `frontend-component-build`, `code-review-web`)
- General accessibility (use `accessibility-audit`)

---

## Required inputs

- The form's purpose (what action, what outcome)
- Current form (URL, screenshot, or fields)
- Current performance (completion rate, spam rate, conversion to next step)
- Downstream system (where submissions go: CRM, email, database, support tool)
- Business context (volume, urgency of leads, cost of false vs missed signups)

---

## The framework: 5 dimensions

Every form decision falls into one of these dimensions.

### Dimension 1: Field strategy

The biggest lever. Every additional field reduces conversion.

**Questions to ask for each field:**
- Is this required to deliver value to the user?
- Is this required to deliver value to the business?
- Can it be inferred from another source (email domain, behavior, context)?
- Can it be asked later (after first contact, on second visit, on settings page)?

**Default rule:** ask for the minimum to make the next step happen. Everything else later.

For a B2B contact form: name and email get you started. Phone, company size, role are nice-to-haves that often hurt conversion more than they help qualification.

For a checkout: country, postal code, address, name, payment. Anything else (referral source, marketing opt-in, account creation) is optional or moved to post-purchase.

### Dimension 2: Field design

How each field looks and behaves.

- **Labels above inputs** beat placeholders. Placeholder labels disappear when typing.
- **Inline labels** (floating labels) work for very compact forms.
- **Single column** for almost every form. Eyes flow vertically.
- **Logical grouping** with visible spacing. Don't put unrelated fields next to each other.
- **Right input type:** `email` for emails, `tel` for phone, `number` for numbers, `date` for dates. Mobile keyboards adapt.
- **Autocomplete attributes:** `autocomplete="email"`, `autocomplete="given-name"`, etc. Browsers and password managers fill them in.
- **Sensible defaults** for fields where one applies (country pre-selected by IP, etc.). Don't default to anything that would mislead if wrong.

### Dimension 3: Validation

Tell users what's wrong, when, and how to fix it.

- **Validate on blur, not on every keystroke.** Inline errors that appear as someone types are jarring.
- **Re-validate on submit** (catch fields the user skipped).
- **Specific messages:** "Email must include @" beats "Invalid email."
- **Position errors next to the field** they refer to.
- **Don't submit a form when there are errors.** Highlight the first errored field. Scroll to it.
- **Validate server-side too.** Client validation is UX. Server validation is correctness.

For format-flexible fields (phone numbers, postal codes), validate liberally. Reject only what's clearly wrong, not what's "non-standard." Many phone formats exist.

### Dimension 4: Spam defense

Public forms attract spam. Plan for it from day one.

**Layered defense:**

1. **Honeypot field.** A hidden field that humans don't fill in but bots do. If it's filled, reject silently. Free, low-friction, surprisingly effective for low-effort spam.
2. **Time-based detection.** Reject submissions completed in under 2-3 seconds (bots) or after very long delays (suspicious sessions).
3. **Rate limiting.** Reject if the same IP submits too many times.
4. **CAPTCHA as a last resort.** Modern invisible CAPTCHAs (hCaptcha, reCAPTCHA v3, Turnstile) are low-friction. Old image CAPTCHAs are conversion-killers.
5. **Behavioral signals.** Did the cursor move? Was there scroll? Modern services track this.
6. **Content filtering.** Reject obvious spam content (links, foreign-language content if your audience is local, common spam words).
7. **Server-side review.** A queue rather than direct delivery to inboxes for high-spam-target forms.

For most contact forms: honeypot + time check + Turnstile (or similar) is sufficient.

### Dimension 5: Submission flow

What happens after submit.

- **Inline success message** for short forms. Don't redirect just to confirm.
- **Confirmation page** for high-value submissions (to provide next steps, set expectations).
- **Email confirmation** for signups, purchases, RSVPs. Always.
- **Save data on errors** so the user doesn't re-enter everything.
- **Optimistic UI** (show success before the server confirms) for low-stakes forms; risky for high-stakes.

For multi-step forms:
- Show progress (3 of 5)
- Save state between steps (in case of refresh or navigation)
- Allow back navigation without losing data
- Validate per step, not just at the end

---

## Workflow

### Step 1: Audit current state

For each form on the site:
- What's its purpose?
- Number of fields, required vs optional
- Current completion rate
- Current spam rate
- Validation rules
- What happens after submit
- Where the data goes downstream

### Step 2: Define success per form

Different forms have different success metrics:
- Lead form: qualified leads (defined by sales)
- Newsletter: confirmed subscriptions (after double opt-in)
- Contact: substantive replies (not just submissions)
- Checkout: successful payments

Track the metric that matters, not just submissions.

### Step 3: Cut fields ruthlessly

Apply the field strategy filter. For each field, answer:
- Required to deliver value? Keep.
- Nice to have? Move to optional or later.
- Used for routing or qualification? Often can be inferred.

A 7-field form becomes a 3-field form. Conversion rises.

### Step 4: Set up spam defense

Before launching a public form:
- Add a honeypot field
- Add time-based detection
- Add rate limiting
- Add a modern CAPTCHA if the form is high-traffic or high-spam

After launch, monitor. Tune layers based on what's actually getting through.

### Step 5: Improve validation

Walk through each field:
- Is validation specific?
- Does it run at the right time (blur or submit, not on keystroke)?
- Are error messages actionable?
- Is server-side validation matching client-side?

### Step 6: Verify accessibility

Critical baseline:
- Every input has an associated label (visually visible or `aria-label`)
- Errors are associated with inputs (`aria-describedby`, `aria-invalid`)
- Focus order matches visual order
- Color isn't the only way to indicate errors
- Form is fully keyboard-navigable

See `accessibility-audit` for the full WCAG audit.

### Step 7: Test downstream

Submit the form. Verify:
- Data lands where it should
- Required fields are populated correctly
- Spam defenses are working (test with a script)
- The user gets the confirmation they expect
- Internal notification is timely

Forms break silently when downstream systems change. Test after any integration update.

### Step 8: Monitor

- Completion rate over time
- Spam rate over time
- Errors per submission (high errors = bad UX)
- Drop-off field (where do people abandon?)

---

## Failure patterns

**Too many fields.** Most B2B contact forms have 3x more fields than they need. Cut.

**Validation that fires while typing.** Annoying. Causes errors before the user has finished.

**Generic error messages.** "Invalid input." Where? Why? Be specific.

**Required fields not marked.** Users discover they're required only after submission fails. Mark required (or, for short forms, mark optional).

**Autocomplete disabled.** "For security." It's almost never a security improvement and always a UX cost. Leave autocomplete on.

**Tab order is broken.** Tab key skips fields or jumps backward. Set `tabindex` only when necessary; use natural DOM order.

**Submit button below the fold.** Especially on mobile. Users don't see it.

**No save on error.** User submits, has one error, returns to the form, all fields empty. Nightmare. Save the state.

**Captcha as the only spam defense.** Captchas are friction. Layered defense beats brute-force friction.

**Captcha visible by default.** Modern CAPTCHAs (Turnstile, reCAPTCHA v3) are invisible most of the time and only escalate when needed. Use those.

**Newsletter signup that's actually a marketing list.** Honor opt-in scope. If the user signed up for product updates, don't add them to the marketing newsletter.

**Confirmation page that's a dead end.** "Thanks for submitting" with no next step. What now? Provide an action (read related content, return to homepage, follow on social).

**No double opt-in for marketing email.** Bots and typos pollute the list. See `email-deliverability` for why this matters.

**Email field accepting `name@` as valid.** Browser spec validation is loose. Validate against an actual format.

**Custom date pickers worse than native.** The native `<input type="date">` is now good on most platforms. Don't reinvent unless you have a specific reason.

**Forms that lose state on refresh.** For long forms, save to localStorage and restore on load.

---

## Output format

A form audit document includes:

- **Form inventory:** every form on the site
- **Per-form review:** purpose, fields, performance
- **Recommendations:** field cuts, validation improvements, spam defense, design changes
- **Spam defense plan:** layers per form
- **Accessibility status:** WCAG compliance per form
- **Downstream integration map:** where each form's data goes
- **Monitoring plan:** what's tracked

---

## If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.

---

## Reference files

- [`references/form-anatomy-checklist.md`](references/form-anatomy-checklist.md): A field-by-field, behavior-by-behavior checklist for auditing or designing a form, covering structure, accessibility, validation, and spam defense.

© rampstackco · MIT · rampstackco/claude-skills

Similar skills

All skills for Frontend and UI →

From the same set102

The whole set →
ux-research ux-research guides teams through research planning, interview guides, participant recruiting, and turning raw qualitative notes into product decisions. CX Codex +1 314installs long-form-content-frameworks long-form-content-frameworks guides the structural design of standalone long-form content, from whitepapers to case studies. It keeps lengthy drafts focused while preventing editorial fluff. CX Codex +1 313installs ads-performance-analytics The ads-performance-analytics skill helps interpret paid media reports, reconcile attribution, and avoid budget decisions based on a single platform metric. CX Codex +1 313installs seo-keyword seo-keyword discovers search queries worth ranking for, classifies them by intent, and groups them into topic clusters. Helps you prioritize what to write based on traffic potential and competitive difficulty. CX Codex +1 312installs seo-competitor seo-competitor is a Claude Code skill that compares your site with competitors across search, content, backlinks, and technical foundations. It surfaces gaps and prioritizes them. CX Codex +1 309installs content-strategy The content-strategy skill plans a content program with editorial positioning, topic pillars, formats, a calendar, governance, and topical authority work. CX Codex +1 309installs analytics-strategy The analytics-strategy skill designs measurement frameworks: event taxonomy, KPI hierarchy, dashboard architecture, and attribution models. Use it to plan analytics from scratch or audit your existing tracking setup. CX Codex +1 309installs funnel-flow-architecture The funnel-flow-architecture skill maps funnel paths across audience segments and stages, connecting entry points to nurture sequences and offers. Use it when growth tools feel disconnected or everyone gets the same flow. CX Codex +1 309installs

Project sponsors

Companies that keep this analytics open