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.
Summary
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.
Recipe
Quick-reference steps - the fastest path from a blank Project to a workable draft.
- Create a Project named after the specific piece of writing or the ongoing body of work, such as "Client Newsletter" or "Novel Draft: Working Title."
- Add custom instructions covering voice, point of view, tone, and any hard style rules.
- Upload one or two reference files, such as a style guide, a character or terminology list, or a previous chapter.
- Ask for the first draft as a document, so Claude opens it in an Artifact rather than pasting it into the chat.
- Revise the Artifact in place with specific, scoped requests, rather than asking for a full rewrite each time.
When to reach for this:
- You are writing more than one piece that shares the same voice, subject, or audience.
- You keep re-explaining the same background, characters, or terminology in separate chats.
- The piece will go through multiple rounds of revision before it is finished.
- You want a consistent starting point for every new chapter, post, or client piece.
Working Example
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:
- The Project's instructions carry voice and structure so they do not need to be restated every month.
- The actual request only supplies what changes each time: the specific tip and the specific project.
- Requesting a document-length piece naturally produces an Artifact, which is the right container for something that will be edited.
- Hard rules, like avoiding jargon and sales pressure, are set once at the Project level instead of repeated per request.
Deep Dive
How It Works
- The Project's custom instructions apply automatically to every new conversation started inside it, so voice and structure stay consistent piece to piece without manual repetition.
- Uploaded reference files, like a style guide or a running character list, are available to every conversation in the Project, not just the one open when they were added.
- The Artifact holding the current draft keeps its own state; each revision request updates that same draft in place rather than generating a fresh, disconnected version in the chat.
- A version history in the Artifact panel lets you step back to an earlier draft if a revision goes the wrong direction.
Editing Requests That Work Well
| 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.
Keeping Voice Consistent Across a Long Project
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.
Gotchas
- Asking for a full rewrite instead of a targeted edit. This discards good parts of the draft along with the parts that needed work. Fix: name the specific section or line that needs to change.
- Letting one Project cover unrelated pieces of writing. A Project mixing a formal client newsletter and a casual personal blog blurs both voices. Fix: split genuinely different writing into separate Projects.
- Never updating reference files as the voice evolves. An early style guide can go stale once real revisions have shaped the actual voice. Fix: periodically refresh the uploaded reference material with recent finished work.
- Treating every reply as a keeper. Not everything Claude drafts is worth building on. Fix: it is fine to discard a draft and ask again with sharper direction rather than salvaging a weak starting point.
- Skipping the Artifact for a substantial piece. Drafting a long piece directly in the chat window makes revision harder to track. Fix: explicitly ask for the draft as a document if Claude does not open an Artifact automatically.
Alternatives
| 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. |
FAQs
Do I need a Project for a single short piece of writing?
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.
How specific should voice instructions be?
Specific enough that you could use them to check a draft yourself. "Warm but not exclamation-heavy" is more useful than "friendly tone."
What is the best way to ask for a revision without losing good parts of the draft?
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.
Should I upload my entire manuscript to the Project?
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.
Can I keep multiple drafts of the same piece side by side?
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.
Does the Project remember earlier chapters automatically?
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.
How do I keep a client-facing piece from sounding like it was written by AI?
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.
What if my writing project has more than one distinct voice, like two characters?
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.
Is it better to draft in small pieces or ask for a full chapter at once?
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.
How do I stop Claude from changing parts of the draft I didn't ask about?
Be explicit about what should stay the same in the same request, such as "keep the opening exactly as-is, only revise the ending."
Should custom instructions include example sentences in the target voice?
Yes, a short example passage is often more effective than describing the voice abstractly, since it gives a concrete pattern to match.
Can this same setup work for non-fiction or business writing, not just creative writing?
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.
Related
- Role-Specific Use Cases Basics - the broader starting point this page builds on.
- Editing and Iterating on an Artifact - a deeper look at scoped revision requests and version history.
- Setting Up a Project with Custom Instructions - a full walkthrough of writing an effective instructions block.
- Role-Based Prompt Checklist by Job Function - more prompt patterns, including several for writers.
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.