Agent skill · Data & Analytics

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

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill multi-step-form-design --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 10
SKILL.md size: 21 KB
Bundled scripts: none
Path: skills/multi-step-form-design/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Guides the design of forms that are split into multiple steps, with explicit progression, conditional fields, and the option to save and resume. It emphasizes breaking complex data collection into coherent steps, using progress indicators to build momentum, and applying logic to skip or tailor fields based on earlier answers. It also addresses when to choose multi-step versus single-page forms and provides criteria for selecting step patterns (Identity, Context, Need, Detail, Confirmation).

How it works

The skill prescribes evaluating whether a form should be multi-step based on field count, natural groupings, and conditional paths. It defines step architecture conventions (Identity, Context, Need, Detail, Confirmation) and sequencing to ensure low-friction to high-friction progression. It describes progress indicators (step counter, progress bar, step list) and highlights risks when indicators misrepresent remaining work. Conditional logic patterns are outlined to show/hide fields, skip steps, adapt language, or route after submission. Save-and-resume mechanics cover when to use them, how users resume (email link, account persistence, anonymous session), and required trust messaging. Validation strategies include per-step, end-only, or hybrid approaches. Drop-off measurement, remediation, and common anti-patterns are also addressed to guide ongoing improvements.

When to use it

Use when scoping a multi-step form for the first time, auditing a long single-page form, deciding whether to break into steps, or designing conditional logic that makes the form adaptive.

What it can touch

The skill references and supports design decisions around form structure, progression, and validation. It does not implement the form itself but provides the architectural guidance for engineers and designers.

Caveats

The guidance emphasizes balance between cognitive load and completion intent and warns about maintenance complexity with conditional logic and dynamic steps. It also stresses truthful progress indicators and clear trust communication for save-and-resume features.

Summary: The skill provides a structured playbook for designing multi-step forms with clear step architecture, progression, conditional logic, and save-and-resume mechanisms to improve completion rates for complex data collection.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. What this skill covers
  2. The multi-step decision: when to break into steps vs keep single-page
  3. Kitchen-sink-single-page vs progress-theater vs genuinely-staged
  4. Step architecture: what belongs on each step
  5. Progress indicator design
  6. Conditional logic
  7. Save-and-resume mechanics
  8. Validation strategy
  9. Drop-off measurement and remediation
  10. Form anti-patterns
  11. Common failure modes
  12. The framework: 12 considerations for multi-step form design
  13. Reference files
  14. Closing: multi-step forms earn completion when each step earns its place
Ships with 9 files
  • references/common-multi-step-form-failures.md
  • references/conditional-logic-patterns.md
  • references/drop-off-measurement-and-remediation.md
  • references/form-anti-patterns.md
  • references/multi-step-decision-criteria.md
  • references/progress-indicator-patterns.md
  • references/save-and-resume-mechanics.md
  • references/step-architecture-patterns.md
  • references/validation-strategy-patterns.md
More from claude-skills
All skills →
About this skill
What does the multi-step-form-design skill do?

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

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill multi-step-form-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going