Grace Leung AI Marketing Team Builder

// When should I use the Grace Leung AI Marketing Team Builder?

Use this skill when you need to systematise recurring marketing workflows into an AI-powered team, or when a single Claude conversation is no longer focused enough to handle the breadth of your marketing function. Ideal for marketers ready to move beyond one-off prompts into a persistent, structured agent system.

// What inputs do I need to build an AI marketing team in Claude Code?

• Brand context filesrequired
  Brand voice guide, style guide, product offerings, and marketing strategy documents to pre-equip agents with brand knowledge.
• Branded templatesrequired
  Existing on-brand templates (decks, social creatives, landing pages, etc.) that agents will study and replicate in style.
• Marketing function maprequired
  A list of the repeatable marketing tasks you actually do every week — the raw material for defining skills and agents.
• Project folder structurerequired
  A root project folder organised into system folders (context, SOPs, templates) and working folders (ads, pages, presentations).
• External API keys
  API keys for any MCP-connected tools (e.g. image generation services) you plan to integrate into skills.
• Task management board
  A shared Notion Kanban board (or equivalent) with task title, details, priority, and status fields for team-AI collaboration.

// What are the core principles behind the AI Marketing Team Builder?

// How do you build an AI marketing team step by step?

1. 1

   Set up your project folder structure

   Create a root brand folder. Inside your marketing subfolder, create system folders (context, SOPs, templates) and working folders (ads, pages, presentations). Think of this as how a real business organises their work — the folder architecture is the team's physical office.

2. 2

   Load brand context into the context folder

   Add your brand voice guide, style guide, product offerings, and marketing strategy before anything else. This is what pre-equips every agent you will build. Do not skip this step — it makes the whole difference in output quality.

3. 3

   Initialise the project by creating the CLAUDE.md file

   Open the project folder in Claude Code and prompt Claude to scan your folder and draft the CLAUDE.md file for you. This is the custom instructions file for your entire project. Treat it as a living document — you will keep updating it, especially after adding agents.

4. 4

   Install official skills via the plugin command

   Use the /plugin slash command to add Anthropic's official skills GitHub repository marketplace, then search for and install the document skills pack. Confirm installation by checking that all official skills appear under the slash command menu.

5. 5

   Map your marketing function

   List every repeatable marketing task you actually do each week. This is your raw material. Each item on this list is a candidate skill. Group naturally related tasks — these groupings will later define your agent roles.

6. 6

   Build skills using the Reference-Based Method

   For each repeatable workflow: (a) place the relevant branded template or visual reference in the templates folder, (b) prompt Claude to analyse it and produce a detailed analysis report, (c) ask Claude to extend the closest official skill and generate a new custom skill based on the template and analysis report. Claude will create a Skills folder with the new skill's assets inside. Aim for one skill per workflow.

7. 7

   Set up MCP connections for skills requiring external tools

   For any skill that calls an external service (e.g. image generation), create a .mcp.json file in your project root folder. This file declares which MCP servers Claude can connect to for this project, along with the required API keys. Restart Claude Code and verify connections via the /mcp slash command before building the dependent skill.

8. 8

   Build your Style Library for creative skills

   Under the templates folder, create a sub-folder (e.g. social-creatives) containing on-brand visual templates and a style guide that describes when each style is appropriate. These serve as visual inspiration — not exact copies — so Claude learns the vibe and applies it generatively.

9. 9

   Create dedicated agents using the /agents command

   Type /agents in the Claude Code terminal, click 'Create New Agent', select 'for this project only', and let Claude generate the Agent MD file. Define: the agent's name, which skills it should use, its tools, default model, colour, and memory location. Each agent gets its own markdown file in an Agents folder defining its role, skills, and core responsibilities. Keep agent roles non-overlapping — a data analyst thinks in numbers and patterns; a content creator thinks in stories and headlines.

10. 10

    Assign skill sets to each agent role

    Match skills to agents by cognitive type, not convenience. Suggested roles: Data Analyst (campaign reporting, data visualisation), Content Creator (blog writing, keyword research, lead magnet creation), Market Researcher (audience and trend research), Creative Designer (social creatives, branded decks), Campaign Strategist (campaign briefs, landing pages). Each agent should have a coherent, focused playbook.

11. 11

    Update CLAUDE.md with agent routing rules

    Before running any complex task, add explicit routing rules to CLAUDE.md telling Claude when to delegate to a sub-agent versus call a skill directly. Rule of thumb: tasks requiring synthesis (research, strategy) benefit from agents; executional, straightforward tasks (single content formats) can be handled by skills alone. These rules make the system self-directing on complex campaigns.

12. 12

    Test the team on a full campaign task

    Give the team a complex, multi-deliverable brief (e.g. 'Launch a [season/theme] campaign — produce market research, campaign brief, social posts, landing page, and ad creatives'). Observe how Claude routes between agents and skills. Expect roughly 10 minutes for a full package. Assess whether all deliverables are thematically connected — coherent campaign narrative is the quality signal.

13. 13

    Connect a shared Notion task board for team-AI collaboration

    Set up a Kanban board with columns for To-Do and Complete, and fields for task title, details, and priority. Prompt Claude to scan pending tasks, assign the appropriate agent, execute by priority, and update the task status to Complete with output file paths included. This is the bridge between your human teammates and your AI agents.

14. 14

    Activate remote control for mobile access

    Type /remote-control in the Claude Code chat to generate a remote control link. Open this link on your mobile device to connect to your local running session and send tasks to your AI team from anywhere. Do not share this link — it grants full control of your session. If context fills up, type 'clear conversation' to reset. Disconnect via the three-dot menu and archive when done. All work saves locally.

// What does the AI Marketing Team Builder look like in practice?

// What mistakes should I avoid when building an AI marketing team?

• Skipping the context loading step — agents built without brand voice guides, style guides, and strategy documents produce generic output that misses brand standards entirely.
• Piling too many skills into one agent or one conversation — this causes Claude to lose focus, the same way one person cannot be writer, analyst, and designer simultaneously. Keep agent roles non-overlapping.
• Using the style library as an exact copy directive rather than visual inspiration — this produces templated, rigid output instead of creatively on-brand work.
• Forgetting to update CLAUDE.md with agent routing rules before running complex tasks — without explicit routing logic, Claude cannot reliably decide when to use an agent versus a skill, degrading system performance on multi-step campaigns.
• Treating CLAUDE.md as a one-off setup file — it must be updated iteratively as you add new agents, skills, and routing rules. It is a living document, not a one-time configuration.
• Sharing the remote control link — it grants full control of your local Claude Code session to anyone who has it.
• Ignoring context limits during remote sessions — if context fills, the session degrades. Use 'clear conversation' to reset rather than continuing in an overloaded context window.

// What do the key terms in the AI Marketing Team Builder mean?

Skill

A reusable workflow module scoped to one specific marketing task (e.g. branded deck creation, social creative design). Skills are the shared playbook that agents can call. One skill per workflow is the target.

Agent (Sub-Agent)

A dedicated, focused AI team member with its own defined role, assigned skill set, tools, and memory. Agents are used when a task requires synthesis, judgment, or orchestration across multiple skills. Defined by an Agent MD file in the Agents folder.

CLAUDE.md

The master custom instructions file for the entire Claude Code project. It tells Claude who is on the team, what each agent does, and — critically — when to delegate to an agent versus call a skill directly. Must be updated iteratively as the system grows.

Reference-Based Method

A skill-building approach where you provide Claude with an existing branded example, have it generate a detailed analysis report of that example's patterns and rules, then build the skill from the analysis. Produces significantly higher fidelity output than blank-prompt skill creation.

Style Library

A folder of on-brand visual templates and an accompanying style guide placed under the templates folder. Serves as visual inspiration for creative skills — Claude studies the vibe and patterns, not a pixel-perfect copy.

System Folders

Reusable infrastructure folders (context, SOPs, templates) that pre-equip agents with brand knowledge and working patterns. Distinct from working folders where agent outputs are saved.

Working Folders

Output destination folders (e.g. ads, pages, presentations) where agents save their produced deliverables. Kept separate from system folders to maintain clear agent orientation.

MCP Connection (.mcp.json)

A configuration file placed in the project root that declares which external MCP servers Claude can connect to for the project, enabling skills to call external tools such as image generation APIs.

Agent Routing Rules

Explicit rules written into CLAUDE.md that define when Claude should delegate a task to a sub-agent versus handle it with a skill call alone. The rule of thumb: synthesis tasks (research, strategy) → agent; executional tasks (single content formats) → skill.

Remote Control

A Claude Code feature activated via /remote-control that generates a link allowing a mobile device to connect to a locally running Claude Code session, enabling task dispatch to AI agents from anywhere.

Context Folder

A system folder containing brand voice guide, style guide, product offerings, and marketing strategy — loaded before any skill or agent is built to pre-equip the entire team with brand knowledge.

// FREQUENTLY ASKED QUESTIONS