Code Editor Field
Edit code, JSON, and config with syntax highlighting instead of a bare textarea.
What it adds
A form field backed by a real code editor: syntax highlighting, a language mode per field, and inline validation that tolerates work in progress.
What your agent is told to do
5
What your agent is told to do
5-
1
Load the editor library lazily, only on views that use it, and render a usable plain textarea until it arrives. It must never block first paint.
-
2
Set the language mode per field from what the field actually holds, and validate against that mode.
-
3
Report syntax errors as you go, but never block typing or reset the content. Half-written JSON is a normal intermediate state; only submission should be gated.
-
4
Preserve the content exactly: tabs versus spaces, trailing whitespace, line endings, and the final newline. An editor that reformats on save destroys diffs.
-
5
Offer an explicit escape hatch to the plain textarea, and use it automatically when the fancy editor cannot initialise.
Edge cases it handles
6
Edge cases it handles
6- Screen readers and browser autofill do not cope with syntax-highlighted layers — the fallback textarea must be a real, labelled control.
- Pasting a very large file must not freeze the tab; cap the size, disable highlighting above a threshold, and say so.
- Tab must indent inside the editor but must not trap keyboard users — give them a documented way out.
- Content saved with CRLF line endings must come back the same way unless the app deliberately normalises them.
- A failed save must keep the buffer intact; never clear the editor on error.
- Highlighting themes must follow the app's light and dark themes, not ship their own colours.
Definition of done
8
Definition of done
8- The editor library is lazily loaded and never blocks initial render.
- Each field highlights and validates using its declared language.
- Invalid intermediate content can be typed freely; only submit is blocked.
- Whitespace, tabs, and line endings survive a save-and-reload round trip.
- A labelled plain-textarea fallback exists and is used when the editor fails.
- Editor colours match the app's theme in both light and dark.
- 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.