Conditional Form Fields
Show only the fields that matter based on what the user already answered.
What it adds
Form fields that appear, disappear, and become required depending on other answers, with the server agreeing about which branch is live.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the forms with fields that only apply in some cases and define, per field, the exact condition that shows it.
-
2
Write down one explicit rule for hidden values: cleared, preserved, or ignored. Apply it consistently — silent submission of a value the user can no longer see is the classic bug here.
-
3
Make 'required' conditional too. A hidden field must never block submission, and a revealed field must be validated.
-
4
Mirror the same branch logic on the server. The client decides what to show; the server decides what is valid.
-
5
Do NOT use display:none alone to hide a field. A visually hidden input is still focusable, still submitted, and still read by screen readers — remove it or disable it properly.
Edge cases it handles
6
Edge cases it handles
6- Editing an existing record must reopen the branch that record was saved with, including nested conditions.
- Revealed fields must be announced to assistive technology without yanking focus away from the control the user just used.
- A chain of conditions must collapse cleanly — hiding a parent must hide and resolve everything under it.
- Layout must not jump when a field appears; reserve space or animate the height.
- A server validation error on a hidden field must reopen the branch containing it rather than showing an error nobody can find.
- Autosave and draft restore must record which branch was active, not just the field values.
Definition of done
8
Definition of done
8- Each conditional field has a stated rule for what happens to its value when hidden.
- Hidden fields are never submitted, never required, and never focusable.
- The server applies the same branch logic as the client.
- Editing an existing record restores the correct branch.
- Newly revealed fields are announced and do not steal focus.
- Errors on fields inside a collapsed branch reveal that branch.
- 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 Section Pattern
Form Section Pattern
Break long forms into labelled sections people can scan instead of read.
What it does
A section pattern grouping related fields under a heading, a description, and its own actions.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/form-section-pattern
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.