<aside> 💡 Use case: a short checklist of what to have ready before you install. The first run needs Claude Code, one folder and four files you write yourself. Every tool account can wait.

</aside>

1. Claude Code, installed and signed in

<aside> 💻 Install Claude Code from your terminal:

</aside>

npm install -g @anthropic-ai/claude-code

<aside> ▶️ Then go into your project folder and start it:

</aside>

cd ai-social-media-team
claude

<aside> 🔑 The first time you run claude, it asks you to sign in. Follow the prompts in the terminal. When you see the Claude Code prompt waiting for you to type, you are ready.

</aside>

2. A folder on your computer

<aside> 📁 One folder holds the whole system. Call it ai-social-media-team and put it anywhere you like, for example in your Documents folder. Every agent, playbook, template, draft and log lives inside it. The next page creates the full folder tree for you with one block of commands.

</aside>

3. The 4 owner files

<aside> 🧑‍💼 These are the four things only you set. The agents read them and can never change them. Write them before the first run.

</aside>

File What you write in it
owner/brand-voice.md How you sound: the words you use, the words you never use, two or three lines that sound exactly like you
owner/budget-cap.md The most the system may suggest spending, and on what. Any spend still waits for your OK
owner/approval-bar.md What may go out without you, and what must always wait in queue/needs-your-ok.md
owner/positioning.md What you stand for, who you are for, and what you are not

<aside> 📋 The templates for all four, with prompts to fill in, are on Owner inputs: voice, budget, approval bar, positioning.

</aside>

4. Tool accounts: start with almost none

<aside> 🌱 Every tool connection is optional at first. The system starts on weekly exports. You download a CSV or a report from a tool you already use and save it into the right brand-os/ folder. The agents read the folder. Later you can swap that export for an API or MCP connection, and nothing else in the system changes.

</aside>

When What you need Why
First run Claude Code and the project files The orchestrator, the Content engine and one playbook run on files alone
First run, if you have them Exports from tools you already use, such as Google Search Console, Google Business Profile or Meta Business Suite Gives the orchestrator something real to score
Later A scheduler such as Metricool So approved posts can be scheduled on every channel
Later The rest of the tools on the board, one department at a time Each department page lists its tools and the job each one does

<aside> 🧭 Every tool, by zone, with its job in this system: The tool map.

</aside>

Checklist

<aside> ✅ Before you go to the next page:

<aside> 👉 Next: Install the project in Claude Code

</aside>