Claude for Writers: Drafting and Editing With Projects
For writers, the two features that matter most are a Project that holds voice and continuity, and an Artifact that holds the draft itself while it goes through revision.
//
Search across all documentation pages
For writers, the two features that matter most are a Project that holds voice and continuity, and an Artifact that holds the draft itself while it goes through revision.
Writing work is repetitive in a specific way: the same voice, the same characters or subject matter, and the same style rules carry across many separate sessions.
A plain chat forgets all of that the moment the conversation ends, which forces a writer to re-explain their world or their house style every single time.
A Project solves that by keeping voice guidance and reference material in one place, available to every new chapter, article, or scene.
An Artifact solves the second problem: a draft is not a single answer, it is something you look at, mark up, and revise, often many times before it is done.
This page walks through setting up a writing Project and then using an Artifact to draft and revise inside it.
Quick-reference steps - the fastest path from a blank Project to a workable draft.
When to reach for this:
Here is a realistic custom-instructions block for a Project set up to draft a recurring client newsletter:
You are helping draft a monthly newsletter for a boutique landscaping company called Fernwood Gardens.
Audience: homeowners who already hired Fernwood at least once, mostly not gardening experts.
Voice: warm, plainspoken, a little playful, never salesy or full of exclamation points.
Structure: one seasonal tip, one short project spotlight, one closing line inviting replies.
Length: 300 to 400 words total.
Never do: use gardening jargon without a plain-language explanation, or push a hard sales pitch.
With that Project in place, a realistic first request inside a new conversation looks like this: "Draft this month's newsletter. The seasonal tip is about mulching before the first frost, and the project spotlight is a backyard patio we just finished for the Alvarez family."
Claude opens the draft as an Artifact rather than a plain chat reply, since it is a substantial piece meant to be revised.
What this demonstrates:
| Request style | Why it works |
|---|---|
| "Tighten the second paragraph, keep the ending as-is." | Names the exact section to change and what to leave alone. |
| "Make the opening line land harder, three options." | Gives Claude a clear creative target instead of a vague "improve this." |
| "Cut this to 250 words without losing the project spotlight." | States a concrete constraint Claude can check its own output against. |
| "Rewrite the whole thing" (used repeatedly) | Discards prior progress and tends to drift further from the original voice each pass. |
Specific, scoped requests keep the Artifact converging toward a finished piece. Broad, repeated "rewrite everything" requests tend to make a draft feel less consistent over time, not more polished.
For an ongoing piece like a novel or a serialized newsletter, upload the most recent finished chapter or issue as a reference file periodically, not just at the start.
This keeps the Project's sense of "current voice" from drifting away from where the actual writing has settled after several rounds of real revision.
If a piece is genuinely long-running, over many months, plan a short voice check-in: read back the custom instructions and confirm they still describe how the writing actually sounds now.
| Alternative | Use When | Don't Use When |
|---|---|---|
| Plain chat, no Project | A single, unrelated piece of writing with no expected repetition. | You are writing several pieces that share a voice or subject. |
| One Artifact, no Project | A single long piece you will revise in one sitting and not return to later. | The piece spans multiple sessions or needs consistent voice with other pieces. |
| Retyping style notes each time | You genuinely only write in this voice once. | You are repeating the same style guidance across many separate chats already. |
Not usually. A Project earns its setup cost once you are writing more than one piece that shares voice, audience, or reference material. A single short piece is fine in plain chat with an Artifact for the draft itself.
Specific enough that you could use them to check a draft yourself. "Warm but not exclamation-heavy" is more useful than "friendly tone."
Name the exact section, line, or issue, such as "the ending feels rushed, expand the last two paragraphs," rather than asking for a general rewrite.
Usually not all at once. Start with a style guide, a character or terminology list, and the most recent finished chapter, then add more only if a conversation is missing context it clearly needs.
The Artifact's version history lets you step back through prior revisions of one draft. For genuinely separate directions you want to compare, ask for them as clearly labeled options in one request rather than juggling multiple Artifacts.
Only what you have uploaded as files or what appears in the same conversation. A Project does not automatically ingest every past conversation, so periodically uploading recent finished work keeps continuity current.
Give specific, checkable voice rules, provide real examples of the target voice as reference files, and edit with targeted requests rather than accepting the first full draft as final.
State each voice explicitly in the instructions and be specific in each drafting request about which voice applies. For very different voices, consider whether two narrower Projects would actually be clearer than one broad one.
Either can work, but smaller pieces are easier to revise precisely. If a full chapter comes back needing broad changes, it is usually faster to have asked for it in two passes.
Be explicit about what should stay the same in the same request, such as "keep the opening exactly as-is, only revise the ending."
Yes, a short example passage is often more effective than describing the voice abstractly, since it gives a concrete pattern to match.
Yes. The same pattern, a Project holding voice and reference material plus an Artifact holding the current draft, applies equally to newsletters, reports, and marketing copy.
Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.
Reviewed by Chris St. John·Last updated Jul 19, 2026