Claude · Module 03 of 8

Writing

Draft, edit, and structure long-form and short-form writing with a consistent voice.

3 lessons12 exercises
Topics & techniques

Long-form

Articles, essays, and documents that hold structure.

4 cards →
Knowledge card
Draft One Section at a Time to Hold Quality
A long-form pattern where you have Claude draft a big document one section at a time — refining each before moving on — rather than generating the whole thing in a single pass.
L2 · Context engineering
Knowledge card
Keep a Running Summary So Long Drafts Stay Coherent
A pattern for long documents where you maintain a short running summary — the key claims made, terms defined, and decisions settled so far — and feed it forward so each new section stays consistent with everything before it.
L3 · Workflows
Knowledge card
Keep a Voice Guide in the Context for Long-Form Writing
Pinning a short, concrete voice guide — do's, don'ts, and two sample sentences — into the context so every part of a long piece sounds like the same author.
L3 · Workflows
Knowledge card
Approve the Outline Before Claude Drafts
A long-form pattern where you have Claude produce a detailed outline — sections, the point of each, the order — and you edit and approve that outline before it writes a single paragraph.
L2 · Context engineering

Editing

Tighten, restructure, and proof existing drafts.

4 cards →
Knowledge card
Cut It to Length Without Losing the Point
An editing pattern for cutting a piece to a target length where you tell Claude the exact target and, crucially, what must survive the cut — the core point, the call to action, the key example — so it trims aggressively without gutting the message.
L2 · Context engineering
Workflow
Edit for One Problem Per Pass
An editing workflow that runs the draft through Claude one concern at a time — structure, then clarity, then tone, then proofreading — instead of asking it to 'make this better' in a single sweep. Each pass has exactly one job.
L2 · Context engineering
Knowledge card
Get a Critique Before You Ask for an Edit
An editing pattern where you first ask Claude to critique your draft — name its weak spots, unclear passages, and unsupported claims — before you ask it to rewrite anything, so the edit targets real problems instead of rewriting on instinct.
L2 · Context engineering
Knowledge card
Make Claude Edit Without Erasing Your Voice
An editing pattern where you explicitly constrain Claude to fix specific problems while preserving your voice — your rhythm, word choices, and quirks — instead of letting an open 'improve this' smooth the draft into generic prose.
L2 · Context engineering

Technical writing

Turn how something works into docs a reader can actually follow.

4 cards →
Knowledge card
Define the Terms You're Quietly Assuming
A technical-writing pattern where you have Claude identify the terms, acronyms, and concepts a piece assumes the reader knows, and define them at first use — pitched to the actual audience rather than to the author.
L2 · Context engineering
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.
L2 · Context engineering
Knowledge card
Lead With a Worked Example, Then Explain
A technical-writing pattern where you have Claude open with a concrete, runnable example — the smallest real case — and only then generalise into the rule, rather than leading with abstract description.
L2 · Context engineering
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.
L2 · Context engineering
Claude for writing

Claude holds structure over length

Claude is particularly strong at long-form and structured writing — the kind that has to stay coherent across many pages rather than reading well for a paragraph and then drifting. Its large context window lets it hold an entire brief, a style guide, and prior sections in mind at once, so a long document keeps a consistent argument and voice. As with any assistant, the output is only as good as the frame: give it the audience, the purpose, the tone, and an example of the standard you want.

Technical writing is a genuine strength

Where Claude pulls ahead of general assistants is technical and reference writing — documentation, specs, explanations that must be accurate as well as clear. It stays faithful to source material, which matters when a wrong sentence is a bug in the docs. The reliable method is the same as with code: give it the real material, ask it to write from that, and edit in focused passes rather than expecting a finished piece in one shot.

The writing topics to explore

This section covers long-form (documents that hold structure), editing (tightening existing drafts), and technical writing (accurate, clear documentation). Pick the card below that matches what you are producing.

Frequently asked
Is Claude good for writing?

Yes — it is especially strong at long-form and technical writing that has to stay coherent and accurate across length. Its large context window lets it hold a full brief and prior sections in mind, keeping a long document consistent in argument and voice.

Is Claude better than ChatGPT for writing?

Many writers prefer Claude for long-form structure, technical accuracy, and staying faithful to source material. ChatGPT has a broader consumer feature set. The best choice depends on the task, and plenty of people use both.

How do I get Claude to write in my voice?

Give it the audience and purpose, describe the tone, and paste an example of writing in the voice you want as a reference. Editing in focused passes afterwards tightens it further without losing the parts that already work.

Can Claude write technical documentation?

Yes, and it is one of its strengths. Provide the real source material and ask Claude to write from it — its tendency to stay faithful to what it is given makes it well suited to docs, specs, and reference writing where accuracy matters.

Test yourself

How well do you write with Claude?

Six questions on drafting, editing, and technical writing with Claude — holding structure over a long piece and keeping your voice through an edit. No sign-up, instant score, and you can share how you did.

  1. Q1 Before Claude drafts a long article, the highest-leverage step is to…
  2. Q2 A long piece keeps contradicting itself and redefining terms it already defined. What fixes it?
  3. Q3 You want every part of a long piece to sound like the same author. What actually works?
  4. Q4 You're cutting a piece to 800 words. What's the critical instruction most people leave out?
  5. Q5 Your draft needs work on structure, clarity, tone, and typos. What's the reliable approach?
  6. Q6 You're explaining a technical concept. Which opening teaches best?
0 / 6 answered