Can a prompt replace Reform?

Build a one-question-at-a-time form builder whose distinguishing feature is capturing partial submissions.

Form definition: an ordered list of questions, each with a type (short text, long text, email, phone, number, single select, multi select, rating, date, file upload, statement), a label, help text, required flag, and validation. Simple branching: a select answer can jump to a named question, and a jump can skip to the end.

Presentation: one question per screen, with the next appearing on submit. Keyboard first — Enter advances, arrow keys move through options, and the whole form is completable without a mouse. A progress indicator showing position, not a percentage, since branching makes percentages wrong. Respect prefers-reduced-motion, and keep every control a real labelled form element so assistive technology works.

Partial capture, which is the point of this build. Create a response record as soon as the first question is answered, and update it after each subsequent answer. A response therefore always exists in one of two states: partial or complete. Rules that make this honest rather than creepy:

- State it on the form, once, in plain words: answers are saved as you go.
- Never save an answer to a field the respondent has typed into but not submitted.
- Give the respondent a way to complete later from the same browser, resuming where they stopped.
- Provide a delete-my-response action reachable from the form, which removes the partial as well as any completed record.

Analytics that fall out of partials for free: for each question, how many respondents reached it and how many answered it, so the question where people abandon is visible. That drop-off table is the most useful artefact this build produces and no completed-responses-only form can show it.

Administration: response list filterable by state, a detail view per response showing the answers in order with timestamps, CSV export of complete, partial, or both, and an email notification on completion.

Spam and abuse: honeypot field, a minimum time-to-complete threshold, per-address rate limiting, submission size limits, and file uploads restricted by type and size and stored outside the web root.

Delivery: each form at a stable slug on its own page, plus an embed script rendering into a shadow root and sized to content.

Out of scope: payment collection, CRM integrations, a template library, and any hosted multi-tenant deployment.