ClaudeTechnical writingLevel 2: Context

How Do You Get Claude to Explain the Jargon in Your Docs?

Tell Claude who the reader is and what they already know, then ask it to find every term that reader might not understand and suggest a short definition at first use. You can't spot these yourself, because you stopped noticing them years ago. Give it your own glossary so it uses your definitions.

Prompt to copy
The reader is [role]. They already understand [what they know]. They don't know [what they don't know]. They'll use this document to [task].

<glossary>
[paste your product's own definitions, if you have them]
</glossary>

<draft>
[paste the draft]
</draft>

List every term, acronym and concept this reader may not know, in the order they first appear. For each one, give:
- The sentence where it first appears
- A definition of 15 words or fewer that fits into that sentence, or a plainer word to use instead
- Where the definition came from: "glossary", "draft" or "general knowledge"

Leave out terms this reader knows. Don't change the draft yet.
reader may not know it →
Draft it, then verifycheck with the term's owner
Define from your glossaryyour meaning, at first use
Leave it alonethe reader already knows it
Use it consistentlyno definition needed
in your glossary →
A rule of thumb, not an Anthropic chart: a term is only jargon relative to a reader, and your glossary beats Claude's guess.

Try it now

  1. 1Paste the prompt with one real doc and a specific reader, like "a new support agent in week one".
  2. 2Check every definition marked "general knowledge" against what your product really does.
  3. 3Reply: "Apply the approved definitions at first use only, and use each term the same way throughout."
  4. 4You'll know it worked when someone from your target audience can read it without asking what a word means.

Use it when

Docs that reach beyond your team, such as onboarding guides, API overviews for partners, compliance docs read by non-lawyers, and internal explainers for new hires. Use it too when your product uses a common word in a special way.

Skip it when

Reference docs for experts. Defining "idempotent" in a page for backend engineers wastes their time. Also skip inline definitions in legal text, where a term's definition must stay in the agreed definitions section, not be rephrased in passing.

Why it works

A term is only jargon relative to a reader, so "remove the jargon" is too vague to act on. Anthropic's prompting guide says the more precisely you explain what you want, the better the result, and it offers a test: show your prompt to a colleague with little context, and if they'd be confused, Claude will be too.

Claude's add-ins treat this as a standard job. Anthropic's Word page lists prompts like "Define this term and use it consistently throughout" and "Flag inconsistent defined terms". The Google Docs help page lists checking for terms that are used but never defined. Definitions need checking, though. Without your source, Claude writes what a term usually means from training, which may not be what your product means by it.

Example

Say your billing guide is going to new customer success hires. It uses "proration", "MRR", "dunning" and "seat". You paste your internal glossary, where "seat" means a paid login and not a license. Claude lists the first three with short definitions, and marks "dunning" as general knowledge because your glossary doesn't have it. "Seat" comes from your glossary. You check the "dunning" definition with finance, and only then have it applied.

Going further

Keep the glossary in project knowledge rather than pasting it each time. Click + in the project's knowledge panel and upload it, and Claude can use it in all chats in the project. If the project grows large enough for retrieval to start, Anthropic recommends naming the specific document in your question, so say "use glossary.md".

For a document already in Word, Claude's add-in reads the whole open document, so you can ask "Is the same party referred to by different names anywhere in this document?" That same question works for products and features, and it often finds more trouble than undefined terms do.

Common mistakes

  • Asking to "simplify this" without naming a reader. Claude has to guess who's confused, and it may strip out terms your reader needs to learn.
  • Defining every term at every use. Define at first use only, or the page becomes hard to read.
  • Accepting definitions from general knowledge where your product differs. Without your source, Claude can only give the usual meaning.
  • Adding a definition to one section while a different name for the same thing stays elsewhere. Ask for a consistency check in the same pass.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course