Claude Code content guides.
Claude Code is Anthropic's agentic coding tool, and in a content system it is the part that reads your files and writes from them: the knowledge base, the voice reference and the platform rules go in, and drafts, carousels and scripts come out. These guides show it doing real content work, and where it needs another tool beside it.
A folder it reads before it writes.
Claude Code for content automation is the place to start. It runs blog posts, carousels and video scripts out of a folder on your own machine, and it is honest about the weak spot: Claude writes and researches well and has no eye, so everything visual is held to a template it is not allowed to touch. One folder the whole system reads explains why the folder matters: Claude Code works on whatever directory it is started in, so the instruction file, the voice file and the knowledge files are the instructions.
The other guides show it next to other tools. Claude Code with Higgsfield connects an image generator through its MCP server, so the session that writes a slide also asks for its picture. n8n or Claude Code splits a pipeline between them: n8n runs on a schedule and moves work between steps, and Claude Code reads the context and writes in your voice. The SEO playbook builds a topic cluster with both, and a quarterly review keeps one current.
How to Write a CLAUDE.md File for a Content Project
Claude Code reads one file before anything else. What a CLAUDE.md for a content project should hold, what to leave out, how long it can be, and how to test that it is followed.
ReadClaude Code vs n8n for Content Automation
Which of the two should hold which part of a content system: judgement over files, or triggers, waiting and logs. How each is maintained, owned and fails, and how to connect them.
Read
How to Keep a Content Operating System From Going Stale
A Content OS goes stale one part at a time. The register, review cadence, triggers, feedback routes and versioning that keep every part current after handover.
Read
Content Atomization: How One Expert Idea Becomes 20 Useful Assets
One expert idea holds a claim, its reasons, its proof, a story and the objection it answers. Atomization pulls those parts apart, maps each to the format it suits, and checks that twenty assets never say the same thing twice.
Read
How to Build a Content Automation System From Scratch
The ten stages of a content automation system in the order they have to be built — the folder, the n8n board, the review gate and the first six weeks, done once from scratch.
Read
Content Automation with n8n
n8n can send you one email every morning with the news in your niche, plus a draft script and a carousel outline waiting for approval. Here is how that pipeline is built, and the one thing it needs from you first.
Read
Content Creation with Claude Code and Higgsfield
Claude Code alone builds carousels out of type and layout. Connect it to Higgsfield over MCP and the same pipeline gets generated visuals. Here is how the connection works, and what it honestly costs.
Read
Claude Code for Content Automation: The Real Version
Blogs, carousels and video scripts out of one terminal. What you have to learn, what files you make, where Claude is genuinely weak, and what it honestly costs.
Read
The SEO Playbook for a Content OS
Search strategies for businesses that have structured their knowledge. How to make your Content OS the most discoverable asset you own — and keep it that way as search changes.
ReadClaude Code, set up for you.
We draft in Claude Code on every system we build, against the client's own files. These pages describe that work, and our content automation pricing sets out what each setup costs.
Talk it through with us.
If something here describes a problem you have, a short conversation is the quickest way to find out whether a system would fix it, and what it would take to build. No pitch: if we can't help, we'll say so.
Start a Conversation