Student Guide
Module 08
Writing with Claude
Claude as Generator and Claude as Editor. Two different roles, two different skill sets. The Editor role is where "it sounds like AI" stops being a problem: your voice goes in, a cleaner version comes out.
Charter Oak Strategic Partners · Claude Mastery Program
- The two writing roles: Generator (create from scratch) and Editor (improve what exists)
- How to fix bad writing with specific editing instructions
- The Revision Loop: a five-step workflow for better writing
- Why Claude as Editor often outperforms Claude as Generator
Generator vs. Editor
| Role | What It Does | When to Use |
|---|---|---|
| Generator | Creates from scratch based on your prompt | When you have nothing written yet |
| Editor | Improves existing work you give it | When you have something to say — preserves your voice |
The complaint “it sounds like AI” disappears when you use Claude as an editor instead of a generator. Your voice goes in. A cleaner version of your voice comes out.
Three Bad Pieces, Three Fixes
Problem: Corporate jargon — “leveraging cross-functional synergies,” “robust pipeline of deliverables.” Every sentence contains a word that means nothing.
Fix: Tell Claude to strip the jargon, lead with the actual update, limit to 200 words. Name what jargon looks like.
Problem: Price increase buried in paragraph four after three paragraphs of context.
Fix: “The price increase is the news. Put it in the first sentence. The context is the justification. Put it after.” Claude follows structural instructions precisely when they are clear.
Problem: “Robust momentum,” “secular tailwinds,” “optimize our go-to-market motion.” Sounds impressive, communicates nothing.
Fix: “Replace every abstract phrase with a concrete fact or number.” “Robust momentum” becomes “revenue grew 12% QoQ.”
The rewrite prompt never says “make it better.” It says exactly what is wrong and exactly what right looks like. That is the difference between a vague request and an editing instruction.
The Revision Loop
Five Steps to Better Writing
- Outline: Give Claude your rough ideas or bullet points. Messy is fine.
- Draft: Ask Claude to write it. Specify voice and constraints.
- Critique: Ask Claude: “What are the three weakest sentences in this draft, and why?”
- Revise: Tell Claude to fix the issues it identified.
- Polish: Specific final instructions. “Tighten the opening. Make the CTA more specific.”
Why it works: it separates generation from evaluation. Claude is good at both. It is less good at both simultaneously.
Exercise: Improve Your Own Writing
Instructions: Bring a piece of your own writing — an email, a report section, a project update. If you do not have one, write one from memory. Then choose:
- Generator path: Start from scratch with a structured prompt
- Editor path: Paste your existing draft and use the Revision Loop
Document the before and after.
Reflection
Questions to Consider
- Did the Generator or Editor approach produce a better result for you? Why?
- What is one piece of writing you produce every week that could benefit from the Revision Loop?
- How would you describe the difference between “make it better” and a specific editing instruction?
Generator vs. Editor
Something to say? Use Editor. Nothing written yet? Use Generator. Editor preserves your voice.
The Revision Loop
Outline → Draft → Critique → Revise → Polish. Separate generation from evaluation.
Editing Instructions
Never “make it better.” Name what is wrong. Define what right looks like. Be specific.