ClaudeTechnical writingLevel 2: Context

How Do You Use Claude to Write Docs People Actually Use?

Give Claude evidence of what readers are really trying to do, such as support tickets, search terms or onboarding questions, and ask it to organize the docs around those tasks. Feature lists are what Claude writes when all it has is a feature list. Add your product reference as the only allowed source of facts.

Prompt to copy
<documents>
<document index="1">
<source>reader evidence: [support tickets / search terms / onboarding questions]</source>
<document_content>[paste or attach]</document_content>
</document>
<document index="2">
<source>product reference</source>
<document_content>[paste or attach]</document_content>
</document>
</documents>

The reader is [who]. From document 1 only, list the 8 tasks people most often try to do, with how many items mention each. Stop and let me approve the list.

Then, for each approved task, write a section:
- A heading phrased as the goal, using the reader's own words
- Numbered steps, from starting point to done
- How they'll know it worked
- The most common way it fails, from document 1, and the fix

Use only document 2 for product facts. After drafting, find a supporting quote in document 2 for each step. If there isn't one, remove the step and mark the place with [].
Feature-first docsfollows the interface
  • Lists every option
  • Reader assembles the steps
  • Doesn't say what goes wrong
Task-first docsfollows the reader's goal
  • Opens with what they want done
  • One path from start to finish
  • Names the common failure
A rule of thumb, not an Anthropic chart: readers usually arrive with a job to do, not an interest in your menu.
  • Chat upload500 MB
    up to 20 files per chat
  • Project knowledge file30 MB
Maximum size per file. Source: Anthropic's upload help page, checked 6 November 2026.

Try it now

  1. 1Export 100 to 200 recent tickets as a .csv, removing customer names and emails first.
  2. 2Click +, choose Add files or photos, and attach it with your product reference. Paste the prompt.
  3. 3Edit the task list Claude gives you, then ask for the sections.
  4. 4You'll know it worked when each heading is something a customer actually said, and every [] shows you a gap in your reference to fill.

Use it when

Help centers, onboarding guides, internal runbooks, and any docs people complain about while still asking support the same questions. It's a strong fit if you have a ticket export, because that's a real record of where people get stuck.

Skip it when

A complete API reference, where readers need every parameter listed in order. Link to it from task pages rather than replacing it. Also hold off if you have no evidence of reader tasks yet. Talk to a few users first, or label the task list as a guess.

Why it works

The tasks have to come from somewhere. If you ask Claude to guess the "top jobs", you get what a typical user of a typical product might want. Upload real tickets instead: Anthropic's upload page lists CSV, TXT, PDF, DOCX and more, at up to 500MB per file and 20 files per chat.

Separate your two sources, one for what people need and one for what's true. Anthropic's docs recommend wrapping each document in its own tags and placing long documents above your request. To hold Claude to your material, its guide to reducing hallucinations suggests telling it to use only the provided documents, then having it find a supporting quote for each claim and remove any claim without one, marking the gap with empty [] brackets.

Example

Say you run a scheduling app, and your help center has a page per settings screen. You upload 150 tickets. If many ask how to move a booking without notifying the customer, that becomes a task, even though the answer spans two settings pages. The section's heading uses the customer's words, not your feature's name. A [] under it means the reference doesn't say what happens to a linked calendar invite, and you need to ask your developers.

Going further

Run this in a project so the reference stays available. Files added to project knowledge are capped at 30MB each, which differs from the 500MB chat limit. On paid plans, retrieval starts when knowledge nears the context limit, and Anthropic says clear filenames and naming specific documents in your question help.

A Word template helps if your docs have a fixed format. Anthropic's Word add-in can draft sections in your document's heading and paragraph styles. For a help center, ask for Output then Docs, and use Export to get Markdown for your docs system.

Common mistakes

  • Asking Claude to invent the tasks. You'll get a believable list with no connection to what your customers struggle with.
  • Uploading raw tickets with names and emails in them. Anonymize first, and check your plan's data settings before using customer data.
  • Letting web search or general knowledge fill product gaps. Your docs should say what your product does, so tell Claude to use only your reference.
  • Treating Claude's ticket counts as analysis. Check a sample of the items behind the top tasks before you reorganize a help center around them.

Sources

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

Related

Beyond the course