AI Translation
Translate app content while preserving structure, placeholders, and product terminology.
What it adds
A translation pipeline over the app's translatable content that keeps source and target linked, protects non-translatable tokens, and routes uncertain output to review.
What your agent is told to do
5
What your agent is told to do
5-
1
Identify what is genuinely translatable and separate it from what is not. Extract placeholders, markup, URLs, identifiers, code, and proper names into protected tokens before generation and restore them afterwards.
-
2
Store every translation with a reference to the exact source version it came from. When the source changes, mark the translation stale and queue it for retranslation rather than leaving a silently outdated string in place.
-
3
Hold a per-language glossary of product terms and their approved renderings, and apply it to every request. A term that translates three ways across the app is worse than leaving it in the source language.
-
4
Run translation through the app's existing background-job system in batches, with a token ceiling per batch and backoff on provider errors. Do not translate on page render or on a user's request path.
-
5
Require review before a translation becomes visible to end users, and let a reviewer approve, edit, or reject per string. Machine output published unreviewed will be found by a customer before it is found by the team.
Edge cases it handles
8
Edge cases it handles
8- Placeholders, markup, URLs, and code fragments come back reordered, translated, or dropped. Verify every protected token is present and unaltered after generation, and reject the string when one is missing rather than shipping a broken interpolation.
- Glossary terms must be enforced after generation as well as requested before it, because a model will happily ignore a term list mid-sentence.
- Word-for-word output loses register. Formality, address form, and politeness level must be specified per language, since the correct choice differs by locale and cannot be inferred from the English source.
- Ambiguous source text — a bare noun that is also a verb, a string with no context, a fragment reused in several places — must be flagged for a human rather than resolved by guessing. Give translators the source context and where the string appears.
- Source and target must stay linked in both directions, so an edit to the source can find every affected translation and a reviewer can always see what a translation was made from.
- Text expansion breaks layouts. Translated strings will run longer than the source in several languages, and the review surface should show where a string is used so the reviewer can catch overflow.
- Right-to-left languages need direction and alignment handled at the layout level; a correct translation rendered in the wrong direction is still broken.
- A refusal, a timeout, or truncated output must leave the previous approved translation in place and mark the string as failed, never fall back to showing the untranslated source where a translation already existed.
Definition of done
9
Definition of done
9- Placeholders, markup, URLs, and code are protected before generation and verified intact after it.
- Each translation records the source version it derives from and is marked stale when the source changes.
- A per-language glossary is applied and enforced on the output.
- Translation runs in background batches with token ceilings and backoff, never on a request path.
- No translation reaches end users without a reviewer approving it.
- Ambiguous source strings are flagged with their usage context for human resolution.
- A failed translation leaves the last approved version visible.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Image Alt Text
AI Image Alt Text
Draft alternative text for uploaded images so screen readers get something useful.
What it does
A suggested alt attribute offered at upload time, editable and confirmable before the image is used.
How it works
- 1 Find every place the app accepts an image and currently stores an empty or absent alt attribute, and offer a suggestion at that point rather than in a separate cleanup screen.
- 2 Ask first whether the image is decorative. A decorative image takes empty alt text, and forcing a description onto it makes the page worse for the people the feature is meant to serve.
- 3 Pass the surrounding context — the page heading, the nearby caption, the purpose of the field — so the suggestion describes the image's role, not just its contents. Do not repeat an existing caption verbatim; a screen reader user would then hear the same sentence twice.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-image-alt-text
AI FAQ Generator
AI FAQ Generator
Produce short question and answer pairs from a document you have already approved.
What it does
A set of concise question-and-answer pairs generated from one nominated source document, each traceable back to the passage it came from.
How it works
- 1 Require the user to nominate a single approved source — a help article, a product page, a policy document — and generate only from that. Do not blend several documents or fall back to general knowledge when the source is thin.
- 2 Store each generated pair with a reference to the passage in the source that supports it, so a reviewer can confirm the answer without rereading the whole document.
- 3 Keep answers to a few sentences and link to the fuller section of the source for anything longer. An FAQ that restates the entire document is just a worse copy of it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-faq-generator
AI Image Captioning
AI Image Captioning
Describe images so they can carry a visible caption and be found by search.
What it does
A generated description stored per image, offered as a draft caption and indexed for search.
How it works
- 1 Store the generated description in its own field and decide explicitly whether each surface shows it, indexes it, or both. Do not write it into the alt attribute, which belongs to AI Image Alt Text and answers a different question.
- 2 Offer the description as a draft caption the user can accept or rewrite, and leave any caption a human already wrote untouched unless they explicitly ask for a replacement.
- 3 Index the description alongside the image's existing metadata so images become findable by what is in them, and reuse the app's existing search infrastructure rather than adding a parallel one.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-image-captioning
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.