The parts of a project
Whatever the client calls them, a good project has five parts. Keeping them separate is the most important setup decision.Choose your structure: by client or by channel
This is the decision that shapes everything. A project is a boundary, and the right boundary depends on how your work is organized — around whose ads, or which platform. Pick the axis that varies most for you; pass the other one in as context inside the project.Fill each part
Instructions — the constitution
The instructions make safe behavior the default, so you never babysit the agent. The non-negotiables for ad ops: confirm before building, create paused, never launch, validate copy, don’t edit it, read before you write, and money needs an explicit yes. Set the agent’s default mode to how you actually work:- Builder-executor — you hand it approved briefs and want campaigns built, verified, and monitored. Copy stays locked; it validates but never rewrites.
- Advisor-overseer — you want the portfolio truth and the decisions; it analyzes and proposes, builds only on request, and the budget calls stay yours.
Copy-paste: starter project instructions
Copy-paste: starter project instructions
Context — what to upload
Give the project the data that makes it sharp:- Brand / voice guidelines (so generated copy sounds like you)
- Target CPA / ROAS by campaign or product line
- Your product feed, offer list, or the thing being advertised
- Naming conventions (campaign / ad-group / UTM structure)
- Audience definitions and exclusion lists
- A recent performance export as a baseline
- Any approved creative that must be used verbatim
Memory — leave it on
Project memory lets the agent reuse prior builds, naming conventions, and decisions across sessions. It’s scoped to the project and private to you. Turn it on and let it accumulate.Connectors — Adspirer is the must-have
- Adspirer (
mcp.adspirer.com/mcp) — the one that matters. Toggle it on and link the exact ad accounts you’ll work in. - A notification channel (Slack or email) — so scheduled tasks can report every run.
- Your brief source (Google Drive, a sheet) — optional, if your specs live there.
Let the agent build your setup for you
You don’t have to fill any of this in by hand. Ask the in-app assistant, or email our agent Otto, something like:“What’s the best way to set up my Adspirer project?”It reads your connected accounts — and any brief, brand doc, or screenshot you share — and generates a setup tailored to you: a project title, ready-to-paste instructions, a prompt library naming your real campaigns, scheduled-task prompts, and a documents + connectors checklist. The docs on this page are the map; the agent fills it with your reality.
Or have it generated from the account itself
The Prompt Engineering Playbook is the packaged version of everything on this page, built from one ad account’s real campaigns, spend, and history. It’s a one-time $39 per ad account — one free on annual plans — and it delivers exactly the parts a project needs:AGENTS.md automatically once
it’s at your project root; chat clients get the same text from the kit page’s one-click Copy
instructions button. See how to install it
for each client.

