Character Limits
Show how much room is left before text gets rejected or cut off.
What it adds
Live remaining-character feedback on limited fields, counting the same way the server does.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every field with a length limit — database column, API constraint, or downstream service — and surface that limit in the UI.
-
2
Count the same units the server counts. If the server counts Unicode characters, do not count UTF-16 code units in the browser; the two disagree on emoji and the user gets rejected for text that looked fine.
-
3
Show remaining count rather than used count once the field is near the limit, and change its emphasis at a threshold rather than colouring it from the start.
-
4
Decide whether to hard-block typing past the limit or allow overflow with a clear error. Hard blocking silently eats pasted text, so prefer allowing overflow and blocking submission.
-
5
Do NOT announce every keystroke to screen readers. Announce only when crossing the warning threshold and when going over.
Edge cases it handles
6
Edge cases it handles
6- Pasting text over the limit must keep the text and show the overage, not truncate it without telling anyone.
- Line breaks must count consistently between client and server, including CRLF versus LF.
- Composed emoji and combining characters must count as the user perceives them, or the rule must be stated.
- Trailing whitespace trimmed by the server must be trimmed by the counter too.
- A field starting over the limit — imported or legacy data — must show the state clearly and still be editable.
- Colour alone must not carry the warning.
Definition of done
8
Definition of done
8- Every length-limited field shows its limit and remaining count.
- The client counts identically to the server, including emoji and line breaks.
- Pasted overflow is preserved and reported rather than silently truncated.
- Threshold and over-limit states are announced once, not on every keystroke.
- The over-limit state is conveyed by more than colour.
- Submission is blocked with a clear message when over the limit.
- 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.