Form Section Pattern
Break long forms into labelled sections people can scan instead of read.
What it adds
A section pattern grouping related fields under a heading, a description, and its own actions.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the forms that have grown past a screenful — settings, profiles, checkout, configuration — and group their fields by the question each group answers, not by the table the columns come from.
-
2
Give each section a heading in the document's heading order and an optional one-line description, so screen reader and keyboard users can jump between sections.
-
3
Allow at most one level of nesting. A section inside a section inside a tab gives the user no orientation and pushes the fields into a narrow gutter.
-
4
When validation fails, expand or scroll to the first section holding an error and mark every other affected section, so nothing stays hidden inside a collapsed group.
-
5
Do not treat sections as a substitute for splitting a genuinely multi-stage process. If the steps are sequential and have their own save points, that is a job for Stepper Component; sections group fields on one page.
Edge cases it handles
7
Edge cases it handles
7- Nesting sections more than one level deep destroys the scannability the pattern exists for — flatten, or split into separate pages.
- A collapsed section containing an invalid field must open on submit; leaving a hidden error with only a generic form-level failure message strands the user with no way to find it.
- Section-level actions such as add another or reset must stay reachable when the section is long, and must not be confused with the form's primary submit.
- On narrow screens the section heading, description, and fields need reduced vertical rhythm rather than the desktop spacing, or the form becomes an endless scroll.
- A section whose fields are all hidden by conditional logic must disappear entirely rather than leaving a heading with nothing under it.
- Collapsed state must not unmount the fields, or their values and validation state will be lost when the user opens the section again.
- Sections must not each own a save button while the form also has one — decide whether saving is per section or per form and apply it consistently.
Definition of done
8
Definition of done
8- Long forms are grouped into sections with headings in correct document order.
- Nesting never exceeds one level.
- Submitting an invalid form reveals every section containing an error.
- Collapsing a section preserves its field values and validation state.
- Sections with no visible fields are removed rather than left empty.
- Spacing adapts on narrow viewports without changing the grouping.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Voice Dictation
Voice Dictation
Put a microphone in text fields so people can speak their input instead of typing it.
What it does
A dictation control on the app's longer text inputs that transcribes speech into the field as the user talks.
How it works
- 1 Add the control to the fields where typing is genuinely tedious: long descriptions, notes, comments, and message bodies. A microphone on a postcode field is clutter.
- 2 Show interim results in the field as they arrive, visually distinct from committed text, so the speaker can see it is working and correct course before they finish.
- 3 Reuse the app's existing Voice Transcription for the server-side path so one recognition configuration and one set of language settings serve both dictation and recorded audio.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-dictation
Help Text Pattern
Help Text Pattern
Put field guidance in one predictable place, phrased the same way every time.
What it does
A consistent treatment for the short explanatory text that sits with a field and its control.
How it works
- 1 Collect the guidance the app currently scatters across placeholders, tooltips, asterisked footnotes, and modal help, and move it into one slot beneath the field.
- 2 Keep guidance that is required to complete the field permanently visible. A format rule hidden behind a hover target is not available to a touch user or a keyboard user.
- 3 Write help as the rule the user needs before typing — the accepted format, the consequence of the choice — not as a restatement of the label.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/help-text-pattern
Form Field Shell
Form Field Shell
Wrap every input in one structure so labels, help, and errors behave the same everywhere.
What it does
A single wrapper owning the label, description, error, and status region around any control in the app.
How it works
- 1 Inventory the app's existing fields and find the variations that have accumulated — label above versus beside, error under versus in a tooltip — then route all of them through one shell.
- 2 Generate a stable identifier per field and use it to link the control to its label, its description, and its error, so the association survives re-renders and does not collide when the same field appears twice on a page.
- 3 Support required, optional, read-only, and disabled as declared states of the shell, and let the shell pass them to the control rather than each screen setting them by hand.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/form-field-shell
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.