<aside> 💡 Use case: build the project folder once, copy every file into place from the guide pages, open it in Claude Code and check that Claude Code can see all 9 agents and all 8 playbooks.

</aside>

Step 1. Create the folder tree

<aside> 📁 Open your terminal, go to where you want the project to live (for example cd ~/Documents), and paste this block. It creates every folder the system uses.

</aside>

mkdir -p ai-social-media-team/.claude/agents
mkdir -p ai-social-media-team/.claude/commands
mkdir -p ai-social-media-team/brand-os/brand-brain
mkdir -p ai-social-media-team/brand-os/signals-seo
mkdir -p ai-social-media-team/brand-os/content
mkdir -p ai-social-media-team/brand-os/creative
mkdir -p ai-social-media-team/brand-os/social
mkdir -p ai-social-media-team/brand-os/reputation
mkdir -p ai-social-media-team/brand-os/conversation
mkdir -p ai-social-media-team/brand-os/reporting
mkdir -p ai-social-media-team/owner
mkdir -p ai-social-media-team/queue
mkdir -p ai-social-media-team/drafts/briefs
mkdir -p ai-social-media-team/logs

<aside> 🗂️ When you are done, the project looks like this:

</aside>

ai-social-media-team/
├── CLAUDE.md
├── README.md
├── .claude/
│   ├── agents/      orchestrator.md + the 8 department files
│   └── commands/    the 8 playbook files
├── brand-os/        README.md + 8 folders, 27 templates
├── owner/           brand-voice.md, budget-cap.md, approval-bar.md, positioning.md
├── queue/           needs-your-ok.md, held-for-voice-review.md
├── drafts/          (department output lands here)
└── logs/            activity.md

Step 2. Where each file comes from

<aside> 📋 Every file is shown in full on a guide page. Open the page, copy the code block, and save it at the path in the left column. Use any plain text editor.

</aside>

File The guide page that has it
CLAUDE.md CLAUDE.md: the rules every agent follows
README.md CLAUDE.md: the rules every agent follows
owner/brand-voice.md, budget-cap.md, approval-bar.md, positioning.md Owner inputs: voice, budget, approval bar, positioning
.claude/agents/orchestrator.md The Orchestrator agent
.claude/agents/search-visibility.md Search visibility
.claude/agents/market-radar.md Market radar
.claude/agents/content-engine.md Content engine
.claude/agents/creative-studio.md Creative studio
.claude/agents/publishing-social.md Publishing & social
.claude/agents/reviews-reputation.md Reviews & reputation
.claude/agents/leads-conversations.md Leads & conversations
.claude/agents/results-roi.md Results & ROI
.claude/commands/search-demand-spikes.md Search demand spikes
.claude/commands/competitor-drops-a-promo.md Competitor drops a promo
.claude/commands/one-star-review-lands.md One-star review lands
.claude/commands/content-calendar-looks-thin.md Content calendar looks thin
.claude/commands/a-post-goes-viral.md A post goes viral
.claude/commands/ranking-drops-a-page.md Ranking drops a page
.claude/commands/ad-creative-fatigues.md Ad creative fatigues
.claude/commands/dm-lead-at-11pm.md DM or lead at 11pm
brand-os/README.md Brand OS: how the folder works
brand-os/brand-brain/ (4 templates) /brand-brain
brand-os/signals-seo/ (4 templates) /signals-seo
brand-os/content/ (4 templates) /content
brand-os/creative/ (3 templates) /creative
brand-os/social/ (3 templates) /social
brand-os/reputation/ (3 templates) /reputation
brand-os/conversation/ (3 templates) /conversation
brand-os/reporting/ (3 templates) /reporting
queue/needs-your-ok.md, queue/held-for-voice-review.md, logs/activity.md Approvals, queues and the kill switch

Step 3. The order to create them

<aside> 🔢 Go in this order. The rules come first, so every agent you add after them already has something to follow.

  1. CLAUDE.md and README.md
  2. The 4 files in owner/ (copy the templates now, fill them in on the first run)
  3. brand-os/README.md and the 27 templates
  4. queue/needs-your-ok.md, queue/held-for-voice-review.md and logs/activity.md
  5. .claude/agents/orchestrator.md, then the 8 department agents
  6. The 8 playbooks in .claude/commands/ </aside>

Step 4. Open the project in Claude Code

<aside> ▶️ Always start Claude Code from inside the project folder. That is how it finds CLAUDE.md, the agents and the commands.

</aside>

cd ~/Documents/ai-social-media-team
claude

<aside> 📜 Claude Code reads CLAUDE.md in the folder you start it from, so the rules apply to the whole session.

</aside>

Step 5. Check Claude Code sees the agents

<aside> 🤖 At the Claude Code prompt, type:

</aside>

/agents

<aside> 👀 What you should see: the project agents listed by name: orchestrator, search-visibility, market-radar, content-engine, creative-studio, publishing-social, reviews-reputation, leads-conversations and results-roi. Claude Code loads every file in .claude/agents/ as a subagent.

</aside>

Step 6. Check Claude Code sees the playbooks