Writing
Technical writing
Turn how something works into docs a reader can actually follow.
Knowledge cards
Best practice
Tell Claude the Reader's Level So It Explains at the Right Altitude
A calibration step: tell Claude exactly who will read the explanation and what they already know, so it pitches the depth, jargon, and examples at the right altitude — the same concept explained differently for an executive, a practitioner, and an implementer.
Best practice
Write Docs From the Reader's Task, Not the Feature List
A documentation approach where you ask Claude to organise around the reader's tasks — the things they're trying to accomplish — rather than cataloguing every feature and setting. The unit of docs is a job to be done, not a UI element.