Terminology Dictionary
Agree on one word per concept, and use it in the UI, the docs, and support.
What it adds
A single authoritative list of the product's concepts with the approved user-facing name for each, its deprecated alternatives, and its grammatical forms.
What your agent is told to do
5
What your agent is told to do
5-
1
Walk the app's navigation, headings, table columns, and settings and record every noun it uses for a concept. Where two words describe the same thing, pick one, record the other as deprecated, and change the strings.
-
2
Record the internal name alongside the user-facing one for every concept whose database table, API field, or code identifier differs from what the interface says, so nobody assumes they must match.
-
3
Give each term its grammatical forms explicitly — singular, plural, the verb where one exists, and whether it is capitalised mid-sentence — because these are exactly the details that drift.
-
4
Make the dictionary the source the localisation files are keyed against, so renaming a concept produces a visible list of translations to revisit rather than silently leaving the old word in every other language.
-
5
Do not rename a concept in the interface without also handling the places the old word persists: URLs, saved searches, exported column headers, help articles, and the words your existing users already say to support.
Edge cases it handles
7
Edge cases it handles
7- The internal name and the user-facing name are allowed to differ, and often should. Recording both prevents an engineer renaming the UI to match a column, or a writer assuming the API exposes the word on screen.
- Retired words do not disappear on the day they are replaced. Keep deprecated terms listed with their replacement so support, search, and old help articles can still resolve them.
- Plurals, possessives, and verb forms are where consistency breaks first, so each entry must carry them rather than leaving them to whoever writes the next string.
- A term change must propagate to every localisation file at once, and the strings awaiting a new translation must be visible rather than quietly falling back to the old wording.
- Terms that are legally or contractually fixed — a plan name, a regulated document type — must be marked as unchangeable.
- Words that already mean something specific in the user's own industry must not be reused for a different concept in the app.
- The sentence patterns, tone, and error structure around these words belong to Microcopy Guidelines; this dictionary settles only which word is correct.
Definition of done
8
Definition of done
8- Each concept has exactly one approved user-facing term.
- Every entry records its internal name where that differs from the interface.
- Singular, plural, verb form, and capitalisation are recorded per term.
- Deprecated terms are listed with their replacement and remain searchable.
- The interface, navigation, help content, and localisation files use the approved terms with no exceptions.
- Renaming a term surfaces the affected translations rather than leaving them stale.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Booking Page
Booking Page
A shareable page where someone picks an open time and confirms it in a few clicks.
What it does
A public scheduling page listing open slots, taking a booking, and confirming it to both sides.
How it works
- 1 Build the visitor path first: pick a date, see open times in their own zone, fill a short form, confirm, and receive an email with the details and a cancellation link. That is the minimum coherent version.
- 2 Derive open slots from the owner's availability rules and existing bookings on the server at request time. Do not trust a slot list the browser has been holding since page load.
- 3 Reuse the app's existing Time Zone-Aware Scheduling for conversion and storage, store every time as an absolute instant, and display it converted to the visitor's detected zone with the zone named on screen.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/booking-page
Audio Chapter Markers
Audio Chapter Markers
Break a long recording into named chapters listeners can see and jump between.
What it does
Named, timestamped chapters on long audio or video, shown in a list and on the scrubber, each addressable by its own link.
How it works
- 1 Store chapters as an ordered list of start times and titles attached to the existing media record, and render them both as a list beside the player and as markers on the scrubber.
- 2 Let an author add, rename, reorder by moving start times, and delete chapters in the player itself, with the current playback position offered as the default start time for a new chapter.
- 3 If chapters are generated automatically, treat the generated set as a first draft. The author's edits must win and must survive the next generation run.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/audio-chapter-markers
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.