Back AI Lab CLAUDE.md starter

Content Pipeline

CLAUDE-content-pipeline.md

For projects building content automation. Encodes one strong opinion: Claude Code first, Make.com only when justified.

A CLAUDE.md file lives in the root of a Claude Code project. When you run Claude Code in that folder, it reads the file automatically and treats the contents as persistent context - preferences, conventions, guardrails. It's the closest thing Claude Code has to a "system prompt" for that project.

This version is built specifically for content automation projects. It encodes a stack, a workflow philosophy, and a clear rule for when to write code vs. when to use a no-code tool.

Core principle
Default to Claude Code for automation. Reach for Make.com only when it's genuinely simpler. Most automations a creator wants - generating posts, batching captions, processing images, scheduling cross-posts - are better as Claude Code scripts. You own the code, debug with logs, version-control everything, and pay nothing per operation. Make.com earns its place when you need event listeners or one-off simple workflows. Not for everything.
Use this if you're building a content automation system - agents, scripts, scheduled jobs, AI image pipelines.
Use this if you've been over-using Make.com and want a clean rule for when each tool is the right choice.
Use this if you want sensible defaults for a Node.js + Supabase + Cloudflare R2 + Gemini stack.
Don't use this if you're starting a fresh, generic Claude Code project - grab the Creator Default starter instead.
01
The Code-first rule
An explicit guideline for when to use Claude Code vs. Make.com. Stops the over-reliance on no-code tools.
02
Tech stack defaults
Node.js, Supabase, Cloudflare R2, Gemini Nano Banana 2, Claude SDK. Easily swappable.
03
Agent conventions
Hub-and-spoke architecture, structured JSON between agents, dry-run modes, checkpointing.
04
Safety guardrails
Never post live without dry-run. No paid API loops without a cost ceiling. Fail loudly.

CLAUDE-content-pipeline.md

CLAUDE.md - lines
1
Download the file using the button above. It'll save as CLAUDE.md.
2
Drop it into the root of your content automation project. If a CLAUDE.md already exists, back it up first.
3
Customise the stack section. If you don't use Supabase, Gemini, or Ayrshare, swap them for what you actually use. The "things you might want to change" section at the bottom calls these out explicitly.
4
Start Claude Code in that folder. The file is read automatically.
Copied