One folder, five content pipelines, zero burnout

Content repurposing sounds simple until you’re staring at a blog post wondering how to turn it into a carousel, an ad set, a newsletter, and an SEO article before lunch. That frustration is exactly what this video tackles head-on. The creator, Grace Leung, walks through a full content system built entirely inside Claude Cowork and Claude Code that turns one project folder into a multi-platform content machine.

What’s new here

This isn’t another “use AI to write a caption” tutorial. The expert designed a three-layer architecture that mirrors how real marketing teams operate:

• Context layer: Your brand voice, audience profiles, product details. This is what keeps outputs sounding like you instead of generic AI slop.
• Skill layer: Reusable instruction sets that tell Claude how to execute specific tasks (carousel design, ad briefs, blog writing).
• Orchestration layer: Claude itself, reading your inputs, running the right skills, and pushing content into organized output folders.

The whole thing is controlled through a simple spreadsheet content planner. Each tab defines input requirements for a different content type, and status columns tell Claude what still needs to be done.

The twist nobody expects

Here’s the part that caught my attention: Claude Cowork spins up parallel agents automatically. You don’t manually create subagents. Drop five carousel briefs into the planner, and it launches five generation tasks at once. The same applies to ad creatives and blog posts. One prompt triggers batch execution across all pending items. That’s not a chatbot workflow; it’s a production pipeline.

Another unexpected detail: Claude Cowork doesn’t automatically read project-level skills the way Claude Code does. The innovator shares a workaround: add instructions to your Claude.MD file pointing to your skill folder, or set it once in global instructions. Miss this step and your skills sit there doing nothing.

🔧 Step-by-step mini-workflow

Here’s how the system flows, broken into the five pipelines the creator demonstrates:

1. Content repurposing: Drop blog posts into a social input folder. Prompt Claude to read them and repurpose into multiple social formats. In the demo, three blog posts became nine social posts, six visuals, LinkedIn posts with structured hooks, and a newsletter draft, all saved in organized output folders.
2. Carousel post generation: 📐 Set up a “style library” folder with reference carousel designs. Include a style guide file so Claude can quickly grasp the visual direction without analyzing every image in real time. The content planner’s carousel tab defines topics and platforms. Claude reads entries with empty status, generates visuals and copy, then updates the planner with output paths.
3. Notion calendar distribution: Content sitting in local folders is invisible to your team. The creator uses a Python script inside the system’s script folder to upload media files to Notion via API. Claude Code reads the content planner, creates Notion entries for items with empty schedule status, uploads visuals, and updates the spreadsheet. Your team opens Notion and everything is already there.
4. Ad creative generation: Build an ad style library with high-performing references (static ads, carousel ads). Include product images and competitor references in an input folder. Claude generates creative briefs first using a dedicated skill, then produces five ad variations per campaign. Twenty-five creatives across five campaigns, all organized by campaign name alongside their briefs.
5. SEO blog writing and publishing: 🔍 Start with content briefs containing topic strategy, content angles, structure, and AI search optimization notes. Claude reads the briefs, writes full drafts with table of contents and key takeaways, generates header images, then pushes everything to WordPress as drafts via a WordPress MCP tool. Seven posts created and uploaded in about fifteen minutes.

✅ Pro tips from the build

• Style libraries over rigid templates: Don’t ask AI to follow a template exactly. Provide reference styles as guidance and let it add variation. The carousel outputs in the demo looked fresh precisely because Claude interpreted the references loosely.
• Include reference images generously: For ad creatives especially, the more product photos and visual references you provide, the closer the output gets to production quality. The creator notes that logos and taglines still need manual fixes, but the creative direction and mood variations are solid for mockups and client briefs.
• Use scheduled tasks wisely: Claude Cowork’s built-in schedule command can automate the entire workflow (e.g., every Friday at 9 AM). One catch: scheduled tasks only run while Claude Desktop is open. Design them to run without human interaction so the agent can execute independently.
• Hit context limits? Use /compact: The built-in slash command frees up context space mid-session. For large batches, split work across separate Claude Code sessions instead of cramming everything into one.
• Always human-review before publishing: The system gets you 80-90% there. Blog drafts need your unique insights and data. Ad creatives need logo and tagline polish. The time savings come from eliminating the blank-page problem, not from removing editorial judgment.

Why this matters for marketing teams

The real value here isn’t any single output. It’s the system design. A content planner spreadsheet acts as the command center. Status columns drive automation. Output folders keep everything organized by campaign and content type. Skills make the whole thing repeatable without re-prompting from scratch every time.

For solo marketers, this eliminates the context-switching tax of jumping between tools. For teams, the Notion integration means content moves from generation to review to publishing without anyone emailing files around.

🎬 The full video walks through every folder structure, prompt, and output in detail. Worth watching if you want to build your own version of this system from scratch.