Individual skill
multi-step-form-design
Designing forms with multiple steps, progress indicators, conditional logic, and save-and-resume mechanics. The discipline of breaking complex data collection into stages that respect cognitive load while maintaining completion intent. Honest about kitchen-sink-single-page (overwhelms before the user starts), progress-theater (steps without genuine staging), and genuinely-staged (each step earns its own page) patterns. Triggers on multi-step form, multi-page form, form wizard, signup wizard, lead form, application form, intake form, configurator, onboarding form. Also triggers when a long form is converting poorly, when an audience is dropping off mid-form, or when a multi-step form is being scoped for the first time.
dist/codex/.agents/skills/multi-step-form-design/SKILL.md
Source commit 9b90db257f7395fab76ff9bfcb808456709f6af3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,047
- Repository last updated
- Oct 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- anthropic Repository topic
- mcp Repository topic
- seo Repository topic
- web-development Repository topic
- agent-skills Repository topic
- claude-code Repository topic
- product-management Repository topic
- web-design Repository topic
- design Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 21,638 bytesSKILL.mdcore · 21,638 bytesreferences/_claude-frontmatter-extras.yamlasset · 594 bytesreferences/common-multi-step-form-failures.mddoc · 9,115 bytesreferences/conditional-logic-patterns.mddoc · 9,842 bytesreferences/drop-off-measurement-and-remediation.mddoc · 10,513 bytesreferences/form-anti-patterns.mddoc · 9,904 bytesreferences/multi-step-decision-criteria.mddoc · 9,397 bytesreferences/progress-indicator-patterns.mddoc · 9,529 bytesreferences/save-and-resume-mechanics.mddoc · 10,296 bytesreferences/step-architecture-patterns.mddoc · 10,195 bytesreferences/validation-strategy-patterns.mddoc · 10,607 bytes
Read excerpt
# Multi-Step Form Design
A senior growth practitioner's playbook for designing forms with multiple steps, progress indicators, conditional logic, and save-and-resume mechanics. The discipline of breaking complex data collection into stages that respect cognitive load while maintaining completion intent.
Most multi-step forms are either kitchen-sink-single-pages dressed up as steps or arbitrary chunking that adds friction without adding clarity. The form looks more sophisticated; the completion rate does not move; the audience is no better served than before.
The multi-step forms that work do something different. Each step represents a coherent unit of cognitive work the user can complete with confidence. Progress indicators reinforce momentum. Conditional logic responds to earlier answers and removes irrelevant fields. The form feels like a guided process, not an obstacle course.
The voice is the senior growth practitioner who has watched multi-step forms convert at twice the single-page rate and watched them collapse to half. Practical, opinionated about when steps add value and when they add friction, willing to call out arbitrary chunking that does not earn its complexity.
When to use this skill: scoping a multi-step form for the first time, auditing a long single-page form that converts poorly, deciding when to break a form into steps and when to keep it on one page, or designing the conditional logic that makes the form feel adaptive.
---