Claude Code for Content Writers: The Complete Setup

Updated January 2026 | 8 min read

Content writers switch contexts constantly. Client A wants formal B2B. Client B wants conversational DTC. Your personal blog is somewhere in between. Newsletter goes out Tuesday. Articles are due Friday. Social posts need to sound spontaneous even though you batched them last Sunday.

Every context switch costs time. You re-read client guidelines. You check past work to remember the voice. You dig through emails to find what they approved last time.

Claude Code with proper setup eliminates that. You type "draft ClientA article" and AI writes in ClientA's voice with their style, their examples, their approved topics. Then you type "draft ClientB newsletter" and it switches completely.

Here's exactly how to set it up.

Why Writers Need AI Memory Most

Writing is voice. Voice is consistency. Consistency requires memory.

Without memory, you're re-training AI every session. "Write like this. No, more casual. No, that's too casual. Remember, this client hates buzzwords. Use short sentences. Wait, shorter."

With memory, you train once. AI remembers. Every session starts where the last one ended.

Three things writers need AI to remember:

Voice rules. How you write. Sentence length, contractions, formality, banned words, rhythm.

Client context. Who they are, what they need, how they sound, what's been covered.

Past work. Examples of good output. Failed attempts. What the client approved. What they hated.

All of this lives in your vault. Claude reads it automatically when you switch clients.

The Writer's CLAUDE.md

Your root CLAUDE.md sits at the top of your Obsidian vault. It's the master instruction set.

For writers, it contains:

# [Your Name] — Content Writer

## WHO

[Your name], freelance writer specializing in [your niche]

**Clients:** [number] active
**Output:** [articles/week or words/month]
**Platforms:** [where you write]
**Schedule:** [when you write]

## WHAT (Domains)

| Domain | Context File | Load when prompt mentions... |
|--------|--------------|------------------------------|
| **Client Work** | `01 - Clients/_context.md` | client, ClientA, ClientB, deliverable, deadline |
| **Personal Content** | `02 - Personal/_context.md` | blog, newsletter, my post, my article |
| **Portfolio** | `03 - Portfolio/_context.md` | portfolio, sample, example |

## VOICE (Default)

[Your natural writing voice — this is what AI uses when you're not writing for a client]

Write direct. Use contractions. Short sentences when they hit harder. Longer ones when the idea needs room.

No corporate speak. No buzzwords. No "solutions" or "innovative" or "cutting-edge."

If it sounds like a press release, rewrite it.

## RULES

1. Read client context before writing anything — voice varies by client
2. Check past work in client folder — don't repeat topics
3. Use client-specific templates when they exist
4. Match the platform — newsletter ≠ blog post ≠ social
5. Ask before publishing or sending — I review before it goes out

## KEY FILES

- `01 - Clients/` — client folders with context and deliverables
- `02 - Personal/Templates/` — my article structures
- `03 - Portfolio/Best-Work.md` — examples of strong writing

This tells AI who you are and how to route requests. When you mention a client name, it loads that client's context.

Client Folder Structure

Each client gets a folder. Inside, you have everything AI needs to write for them.

/01 - Clients/
  /_context.md  [overview of all clients]
  /ClientA/
    /_context.md  [ClientA specific]
    /Style-Guide.md
    /Topics-Covered.md
    /Deliverables/
    /Templates/
  /ClientB/
    /_context.md
    /Style-Guide.md
    /Topics-Covered.md
    /Deliverables/
    /Templates/

When you tell Claude "write for ClientA," it reads ClientA/_context.md and knows everything about that client.

ClientA/_context.md Example

# ClientA Context

## Overview
ClientA is a B2B SaaS company selling project management tools to remote teams. Target audience: mid-market operations managers, 100-500 employee companies.

## Contact
Sarah Johnson — Content Director — sarah@clienta.com
Prefers email, responds within 24hrs, friendly but professional

## Voice
**Tone:** Professional but approachable. Helpful expert, not salesy.
**Formality:** Business casual. Use "you" and "we." Contractions are fine.
**Sentence length:** Mix. Avoid walls of text.
**POV:** Usually second person (you) for blog, first person (we) for company updates

## Banned Words/Phrases
- "Cutting-edge"
- "Revolutionary"
- "Game-changer"
- Any corporate jargon Sarah would roll her eyes at

## What Works
- Practical how-to content
- Real examples from their customer stories
- Lists and actionable steps
- Clear subheadings (skim-friendly)

## What Doesn't
- Theory without application
- Long intros (get to the point)
- Overly clever analogies
- Trying too hard to be funny

## Current Projects
- Blog articles: 2/month, 1200-1500 words, SEO-focused
- Newsletter: weekly, 800 words, more conversational
- Case studies: quarterly, 2000 words, interview-based

## Topics Covered
See [[ClientA-Topics-Covered]] for full list

## Templates
- [[ClientA-Blog-Template]]
- [[ClientA-Newsletter-Template]]
- [[ClientA-Case-Study-Template]]

## Deadlines
Blog drafts due 5 days before publish date
Newsletter draft due Monday 9am for Thursday send

That's everything Claude needs to write for this client. Voice, banned words, what works, what doesn't, current projects, templates.

You don't copy-paste this into the chat. It's in your vault. Claude reads it automatically when you mention ClientA.

Style Guide Files

Each client's Style-Guide.md holds the technical details.

# ClientA Style Guide

## Formatting
- Headers: Title case
- Subheadings: Sentence case
- Lists: Capitalize first word, no ending punctuation unless full sentence
- Em dashes: Use — with spaces

## Grammar/Usage
- Oxford comma: Yes
- Numbers: Spell out one through nine, numerals for 10+
- Contractions: Allowed
- Passive voice: Avoid unless necessary

## SEO Requirements
- Title: 50-60 characters
- Meta description: 150-160 characters
- H1: Include target keyword
- Subheadings: Natural keyword variation, not forced
- Internal links: 2-3 per article to relevant ClientA content
- External links: Only to authoritative sources

## Brand Terms
- "ClientA" — not "Client A" or "clientA"
- "Project Management Hub" — capitalized, their flagship feature
- "remote teams" — lowercase unless starting sentence

## Images
- Featured image: 1200×630px
- In-article images: 800px wide minimum
- Alt text required for all images
- Credit stock photos in caption

When Claude drafts content for ClientA, it follows these rules automatically. No manual checking. No post-draft cleanup.

Topics-Covered Files

This prevents repeating yourself. List everything you've already written for the client.

# ClientA Topics Covered

## 2026
- 2026-01-15: "How to Run Effective Remote Standups"
- 2026-01-03: "Project Management Metrics That Actually Matter"

## 2025-Q4
- 2025-12-18: "5 Ways to Keep Remote Teams Engaged During the Holidays"
- 2025-12-05: "Time Tracking: Why Most Teams Get It Wrong"
- 2025-11-20: "Building a Remote-First Company Culture"

## 2025-Q3
[...]

## Topic Ideas (Not Yet Written)
- Async communication best practices
- Remote onboarding checklist
- Managing projects across timezones
- When to use synchronous vs asynchronous meetings

Before suggesting topics, Claude checks this file. It won't suggest something you wrote three months ago.

Template System

Templates are structure, not fill-in-the-blank. They show AI how you organize content for each client.

ClientA Blog Template:

# [Article Title — Include Primary Keyword]

**Meta description:** [150-160 characters, include keyword]

## Introduction (2-3 paragraphs)
- Hook: Problem or question
- Context: Why this matters
- Promise: What reader will learn

## [Main Point 1]
- Explanation
- Example or data point
- Actionable takeaway

## [Main Point 2]
[Same structure]

## [Main Point 3]
[Same structure]

## How ClientA Helps
[One paragraph connecting article topic to ClientA's product]
[Natural, not salesy]

## Conclusion
- Summary of main points
- Call to action (try ClientA, read related article, etc.)

**Internal links to include:**
- [Related ClientA article 1]
- [Related ClientA article 2]

**External sources to cite:**
- [Authoritative source on this topic]

When you tell Claude "write ClientA blog on remote standups," it uses this structure, ClientA's voice from the context file, and their style guide rules.

Personal Content Setup

Your personal content has a separate folder with its own voice rules.

/02 - Personal/
  /_context.md
  /Blog/
  /Newsletter/
  /Social/
  /Templates/

Personal/_context.md:

# Personal Content Context

## Platforms
- Blog: [your domain] — Long-form, 1500-2500 words
- Newsletter: [platform] — [subscribers] subscribers, weekly
- Twitter/X: Daily thoughts, 1-3 tweets
- LinkedIn: Professional takes, 2x/week

## Voice
This is MY voice. Not a client's.

[Describe your actual writing voice]
- More casual than client work
- Personal stories and examples
- Opinions I can't share in client content
- Experiments with style and format

## Topics I Cover
- [Your niche]
- [Related topics]
- [Personal interests]

## Topics I Avoid
- [Things you don't write about publicly]
- [Controversial areas]

## Newsletter Structure
- Opening: Personal anecdote or observation
- Main content: Teach one thing
- Examples: 2-3 concrete ones
- Call to action: Reply, share, or try something
- P.S.: Additional thought or link

## Posting Schedule
- Newsletter: Every Tuesday 7am
- Blog: 2x/month, Mondays
- Twitter: Daily
- LinkedIn: Tuesday and Thursday

Now when you tell Claude "draft my newsletter," it switches to your voice, uses your topics, follows your structure.

Portfolio Management

A Portfolio folder holds your best work. When you need writing samples or want AI to match a specific quality level, it references these.

/03 - Portfolio/
  /Best-Work.md
  /By-Niche/
  /By-Format/

Best-Work.md:

# Portfolio: Best Work

## Top 5 Writing Samples

**1. [Article Title]** — [[Link to file or URL]]
Why it's strong: [Clear value prop, engaging intro, data-driven, etc.]
Client/publication: [Where it appeared]
Results: [Traffic, engagement, conversions if available]

**2. [Article Title]**
[Same structure]

[...]

## By Format
- **Long-form guides:** [[Sample 1]], [[Sample 2]]
- **Case studies:** [[Sample 1]], [[Sample 2]]
- **Newsletter:** [[Sample 1]], [[Sample 2]]
- **Thought leadership:** [[Sample 1]], [[Sample 2]]

## By Niche
- **SaaS/Tech:** [[Sample 1]], [[Sample 2]]
- **Marketing:** [[Sample 1]], [[Sample 2]]
- **Remote work:** [[Sample 1]], [[Sample 2]]

When a prospect asks for samples, you tell Claude "show me portfolio samples for SaaS long-form guides" and it pulls the right ones.

Daily Writing Workflow

Here's what actually using this system looks like.

Morning: "Show me this week's deadlines."

Claude reads your client context files, lists what's due.

Start writing: "Draft ClientA blog on async communication."

Claude loads ClientA context, checks Topics-Covered to ensure it's not a repeat, uses the blog template, writes in ClientA's voice following their style guide.

You review, edit, save to ClientA/Deliverables/.

Switch clients: "Draft ClientB newsletter intro."

Claude switches to ClientB context. Different voice. Different structure. Different rules. You didn't re-explain anything. It just knows.

Personal content: "Draft my newsletter on AI memory systems."

Claude switches to your personal voice. Uses your newsletter structure. Pulls from your topics.

The context switching happens automatically because your vault has the structure.

What You Get

With this setup:

• No more re-reading client guidelines before every draft
• No more "wait, what's their voice again?"
• No more checking if you've covered this topic before
• No more copy-pasting from past work to remind AI
• No more accidentally using ClientA's voice for ClientB

You switch clients by mentioning their name. AI handles the rest.

Setup Checklist

Step 1: Create root CLAUDE.md with your voice and routing table (30 minutes)

Step 2: Create client folders with context files (1 hour for all clients)

Step 3: Write style guides for each client (30 minutes per client, do one at a time)

Step 4: Log past topics in Topics-Covered files (15 minutes per client)

Step 5: Create templates for each content type (1 hour total)

Step 6: Set up personal content folder and context (30 minutes)

Step 7: Test: ask Claude to draft something for each client, check if voice and style match (15 minutes)

Total setup time: About 4 hours. After that, it's just updates when things change.

Maintenance

After each deliverable: Add the topic to Topics-Covered. Takes 20 seconds.

After client meetings: Update context file with new guidelines or preferences. Takes 2 minutes.

Weekly: Check deadlines in client contexts. Update status of active projects.

Monthly: Review voice rules. If AI's drifting from what you want, refine the voice section.

That's it. The system maintains itself as you work.