The Content System
Drop in one source — a transcript, an idea, a link. The Content Coach orchestrator runs it through six specialist modules and hands back finished, on-brand posts, scheduled to every platform. All directly inside Claude.
One input, seven roles, every output
Inputs flow into the orchestrator. It delegates to six workers, grades the result, and only ships what passes.
Content Coach
Manages delegation, synthesises worker outputs, and enforces the 10-day SEO refresh cycle.
Brand Brief
Captures business, audience, CTA and voice.
Viral Hooks
Proven hook frameworks.
Gatekeeper · 0.85Post Writer
Writes platform-specific posts.
WorkerPost Grader
Scores and improves content.
WorkerRepurpose
Turns one source into many posts.
Post Scheduler
Schedules approved posts.
QA gateGated, audited, self-healing
Every module reports to a shared audit log. Two gatekeepers stand between an idea and a published post.
Conversion Hook Engine
Nothing proceeds until the hook clears the bar.
Content Engine
Does the making — words and visuals.
- Copywriting
- Visual generation
- Quality audit on every pass
Final Delivery Gatekeeper
Last check before anything ships.
- File integrity
- Metadata compliance
- Brand alignment
The system's standing orders
See the pipeline think
A simulated run of the system trace log — the real records written to system_trace_log.json.
This page is a working visual model of the Claude Content System (orchestrator-worker architecture v2.1). It documents the design — connect your own brand context, connectors, and scheduler to run it live. The trace above is illustrative.