AI Knowledge Base Drafting
Turn a solved support issue into a help article draft a writer can finish.
What it adds
A structured, unpublished help article draft generated from a resolved ticket or a set of product notes, with unverified content marked and customer details removed.
What your agent is told to do
5
What your agent is told to do
5-
1
Take a resolved ticket thread or a set of product notes as input and produce a draft in the app's existing article structure — title, summary, prerequisites, steps, related links — rather than one block of prose.
-
2
Strip customer identity before the content is sent anywhere: names, addresses, account identifiers, order numbers, and anything else that identifies the person or their organisation. Remove it at the point the input is assembled.
-
3
Mark the steps that were confirmed to resolve the issue separately from the ones that were tried and abandoned during troubleshooting. A draft that presents a failed experiment as instruction is worse than no draft.
-
4
Pass the app's current feature names and interface labels in as reference material and require the draft to use them, so articles do not describe screens with names the product stopped using.
-
5
Create the article in draft state only, in the app's existing publishing workflow. This brief produces long-form articles from solved issues; short question-and-answer pairs from an already-approved document belong to AI FAQ Generator.
Edge cases it handles
8
Edge cases it handles
8- One customer's ticket becomes public documentation here. Any residual identifying detail — a company name in a log line, an email in a screenshot path — is a disclosure, so redaction must run before generation and be checked after it.
- Troubleshooting threads are full of dead ends. Steps that did not work must be excluded or clearly labelled, and the draft must state which sequence was actually verified to fix the problem.
- Stale terminology makes an article unusable even when the steps are right. If a label in the draft does not match anything in the current product, flag it for the writer rather than publishing it.
- Screenshots and interface captures cannot be generated. Mark the places one is needed with a note on what it should show, and leave the gap visible rather than describing an image that does not exist.
- Nothing generated here reaches customers without a human publishing it. Draft state is the default and there is no automatic publish path.
- A refusal, timeout, or malformed structure must leave no partial article behind. Either the full draft is created or the attempt is discarded with an error the requester can see.
- A ticket containing credentials, tokens, or configuration secrets must be refused as an input rather than redacted and used.
- Enforce a length ceiling and a per-workspace limit on drafting runs so a bulk import of resolved tickets cannot generate hundreds of articles at unbounded cost.
Definition of done
9
Definition of done
9- Drafts follow the app's existing article structure rather than arriving as undifferentiated prose.
- Customer-identifying and confidential details are removed before generation and verified absent after.
- Verified resolution steps are distinguished from abandoned troubleshooting attempts.
- Product names and interface labels match the current product, with mismatches flagged for the writer.
- Places requiring a human-captured screenshot are marked with what the image should show.
- Articles remain in draft until a person publishes them, with no automatic publish path.
- Drafting runs are capped per workspace and produce no partial article on failure.
- 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 Translation
AI Translation
Translate app content while preserving structure, placeholders, and product terminology.
What it does
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.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-translation
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.