--- title: "Set up Claude Code so every client draft starts in the right voice" description: "A folder setup for content writers: one CLAUDE.md, one folder per client, style guides, topic logs, and templates that Claude Code reads before it drafts." canonical: "https://scalewithsearch.com/articles/claude-code-for-content-writers" date: "2026-01-28" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Set up Claude Code so every client draft starts in the right voice. Client A wants formal B2B copy. Client B wants a conversational direct-to-consumer tone. Your own blog sits between the two. The newsletter goes out Tuesday, articles are due Friday, and the social posts must sound spontaneous although you wrote them in a batch last Sunday. Each switch costs time. You reread the client guidelines. You check past work to recall the voice. You search email for what the client approved last time. Claude Code can hold that context for you. Type "draft ClientA article," and Claude Code writes in ClientA's voice with ClientA's style rules, examples, and approved topics. Type "draft ClientB newsletter," and it loads ClientB instead. This article shows the folder setup that makes the switch work. ## Know what a writer needs AI to remember Writing is voice, and voice depends on consistency. Without memory, you train the AI again each session. "Write like this. No, more casual. No, too casual. This client hates buzzwords. Use short sentences. Shorter." With memory, you write the rules once, and each session starts from them. Writers need three kinds of record: | Record | What it holds | |---|---| | Voice rules | Sentence length, contractions, formality, banned words, rhythm | | Client context | Who the client is, what they need, how they sound, what you already covered | | Past work | Strong examples, failed attempts, what the client approved, what the client rejected | All three live in an Obsidian vault as Markdown files. Claude Code reads them when you name a client. The [brand memory article](/articles/ai-brand-memory-content-creation) covers the voice record in more depth. ## Before you start Claude Code runs in a terminal: Terminal on a Mac, or Command Prompt or PowerShell on Windows. You install it with one command. The hardest part of the setup is the `CLAUDE.md` file, which is a text document. Obsidian is a note app that stores plain text files. You write notes in Markdown, which is text with simple marks: `**word**` for bold and `#` for a heading. If you can write an email, you can use Obsidian. You do not need to leave Notion or Google Docs. Many writers keep Notion for project management and use Obsidian with Claude Code for the work that depends on stored context. ## Write the root CLAUDE.md The root `CLAUDE.md` sits at the top of the vault. It holds your identity, your routing table, your default voice, and your rules. For a writer, it looks like this: ``` # [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. AI uses this when you are 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 the client folder. Do not repeat topics. 3. Use client-specific templates when they exist. 4. Match the platform. A newsletter is not a blog post, and neither is a social post. 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 ``` The routing table tells Claude Code which context file to load. When you mention a client name, it reads that client's file. The [CLAUDE.md template article](/articles/claude-md-template-business-context) shows the same pattern for a business owner. ## Give each client a folder Each client gets one folder. Inside it is everything Claude Code needs to write for that client. ``` /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 say "write for ClientA," Claude Code reads `ClientA/_context.md`. Keep each client's material inside its own folder, so one client's voice or facts never leak into another client's draft. The [client context separation article](/articles/separate-client-context-before-agent-work) explains how to test that boundary. A client context file for a B2B software client looks like this: ``` # 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 Content Director: name and email in the client record. 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 the content director rejects ## 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 file holds the voice, the banned words, what works, what fails, the current projects, the templates, and the deadlines. You do not paste it into a chat. Claude Code reads it from the vault. ## Add a style guide for the mechanical rules The context file holds the voice. `Style-Guide.md` holds the mechanical rules. ``` # ClientA Style Guide ## Formatting - Headers: Title case - Subheadings: Sentence case - Lists: Capitalize first word, no ending punctuation unless full sentence - Em dashes: allowed, with a space on each side ## 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 a sentence ## Images - Featured image: 1200×630px - In-article images: 800px wide minimum - Alt text required for all images - Credit stock photos in caption ``` Claude Code applies these rules in the draft. You still review the draft, but you spend the review on substance, not on comma style. ## Log every topic you cover `Topics-Covered.md` stops you from repeating yourself. List everything you already wrote for the client, plus the ideas you have not written yet. ``` # 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 ``` Tell Claude Code to check this file before it suggests topics. It will not propose the article you wrote three months ago. ## Write templates as structure A template shows how you organize one content type for one client. It is a structure, not a form to fill in. ``` # [Article title with the 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] ``` For "write ClientA blog on remote standups," Claude Code combines this structure, the voice in the context file, and the rules in the style guide. ## Keep your own content in a separate folder Your own content gets a folder with its own voice rules: ``` /02 - Personal/ /_context.md /Blog/ /Newsletter/ /Social/ /Templates/ ``` The personal context file records the platforms and their formats. Examples are a long-form blog of 1,500 to 2,500 words, a weekly newsletter, daily posts on X, and LinkedIn posts twice a week. It describes your own voice, which is usually more casual than client work. It holds personal stories, opinions you cannot put in client content, and experiments with form. It lists the topics you cover and the topics you avoid in public. It also sets the newsletter structure. Open with a personal anecdote or observation. Teach one thing. Give two or three concrete examples. End with a call to reply, share, or try something, and add a P.S. with one more thought or link. The file ends with the schedule. For example: newsletter Tuesday at 7 a.m., blog twice a month on Mondays, X daily, and LinkedIn on Tuesday and Thursday. For "draft my newsletter," Claude Code loads this file and uses your voice, topics, and structure. ## Keep a portfolio file A portfolio folder holds your best work. Claude Code uses it to match a quality level, and you use it to answer a prospect who asks for samples. ``` /03 - Portfolio/ /Best-Work.md /By-Niche/ /By-Format/ ``` `Best-Work.md` lists your top five samples. Each entry carries the title and link, why the piece is strong, where it appeared, and its results when you have them. Below that, group samples by format (long-form guides, case studies, newsletters, thought leadership) and by niche (SaaS, marketing, remote work). Ask Claude Code for "portfolio samples for SaaS long-form guides," and it returns the matching entries. ## Worked example: one writing day In the morning, you ask Claude Code, "Show me this week's deadlines." It reads the client context files and lists what is due. You ask for "Draft ClientA blog on async communication." Claude Code loads the ClientA context. It checks `Topics-Covered.md` and finds async communication on the unwritten list. It applies the blog template, writes in ClientA's voice, and follows the style guide. You review, edit, and save the draft to `ClientA/Deliverables/`. Next, you ask for "Draft ClientB newsletter intro." Claude Code loads the ClientB context: a different voice, structure, and rule set. You did not explain anything again. Last, you ask for "Draft my newsletter on AI memory systems." Claude Code switches to your personal voice and your newsletter structure. The folder structure makes each switch possible. Without it, you would reread guidelines before each draft and confirm each client's voice. You would check past topics by hand and paste old work into the chat as a reminder. You would also risk ClientA's voice in a ClientB draft. ## Set up the system in about four hours 1. Create the root `CLAUDE.md` with your voice and routing table. Allow 30 minutes. 2. Create the client folders and context files. Allow 1 hour for all clients. 3. Write a style guide for each client. Allow 30 minutes per client, one client at a time. 4. Log past topics in each `Topics-Covered.md`. Allow 15 minutes per client. 5. Create templates for each content type. Allow 1 hour in total. 6. Set up the personal folder and its context file. Allow 30 minutes. 7. Test the setup. Ask for one draft per client, and check that the voice and style match. Allow 15 minutes. The total is about four hours for a small client list. After that, you update the files when things change. ## Maintain the files as you work After each deliverable, add the topic to `Topics-Covered.md`. That takes about 20 seconds. After a client meeting, update the context file with new guidelines or preferences. That takes about 2 minutes. Each week, check the deadlines in the client context files and update the status of active projects. Each month, review the voice rules. If the drafts drift from what you want, refine the voice section. The files stay useful only while someone keeps them current. The [freelancer memory article](/articles/ai-memory-for-freelancers) covers the same upkeep for a wider set of client work. ## Related: AI memory - [Measure AI first-draft editing time and cut it with persistent context](/articles/ai-first-draft-accuracy) - [Give AI a client file so email drafts start with the right context](/articles/ai-memory-before-and-after-email) - [Write voice rules that make AI drafts sound like you](/articles/ai-writing-sounds-generic) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```