Claude Code V2 with a well-structured CLAUDE.md file, a curated MCP server stack, and custom slash commands is one of the most capable AI-assisted development setups available. CLAUDE.md acts as persistent project memory loaded at every session; MCP servers extend Claude's reach to files, databases, and live documentation; and custom commands encode repeatable workflows so they run consistently without drift.
.claude/commands/ make repeatable workflows consistent across every developer and agent on the project — human or AI..claude/commands/ directory as engineering infrastructure: version-control them, review them like code, and update them as the project evolves.CLAUDE.md is Claude Code's project memory file — a markdown document that sits at the root of your project and is automatically loaded into context at the start of every session. [1] Without it, Claude Code starts cold every time. With a well-crafted one, it starts as a senior engineer who already knows your stack, your conventions, your constraints, and your current goals.
A practical question that came up in the r/ClaudeAI community thread on this topic is how much to put in CLAUDE.md versus handling through in-session prompting. The answer practitioners have landed on: anything you'd need to re-explain more than once goes into CLAUDE.md; anything you'd say once in a session stays in the session. That mental model keeps the file lean and genuinely useful.
A production CLAUDE.md is structured information Claude can parse quickly, not a wall of text. Here are the sections worth including:
For agent-focused projects — like Buddy, the open-source Google Ads agent — the CLAUDE.md needs sections most tutorials skip:
MCP servers are external processes that Claude Code connects to, giving it capabilities beyond text generation — reading files, querying databases, browsing documentation, calling APIs, and manipulating browser state. [2] The value depends entirely on which servers you configure and how. Think of them as Claude's hands: without them, it can think and write; with them, it can act.
For a deeper look at how these pieces fit together, see what's the difference between Claude Code and MCP.
| MCP Server | What It Does | Best For | Priority |
|---|---|---|---|
| Context7 | Fetches live documentation for libraries & frameworks | Any project using actively-updated dependencies | Essential |
| Filesystem | Read/write files outside the working directory | Multi-repo work, config management | Essential |
| Brave Search | Real-time web search from within Claude Code | Research, error diagnosis, checking current APIs | High |
| GitHub | PR creation, issue management, repo operations | Teams, open-source projects | High |
| Puppeteer / Playwright | Browser automation & scraping | Testing, data collection, UI validation | Medium |
| PostgreSQL / SQLite | Direct database querying | Data-heavy applications | Project-specific |
AI coding assistants have a training data cutoff, and libraries like the Google Ads API, LangChain, or Next.js change fast enough that hallucinated method signatures and deprecated patterns are a recurring problem. [3] Context7 solves this by fetching up-to-date documentation dynamically when Claude needs it, rather than relying on potentially stale training data.
In practice — working on Google Ads API integrations — this has meaningfully reduced debugging cycles on dependencies that change quarterly. I'd estimate 40–60% fewer "why isn't this method working" cycles on fast-moving libraries, based on my own project experience.
For step-by-step MCP configuration guidance, setting up MCP servers in Claude Code covers the installation ritual in detail.
Custom slash commands let you define repeatable workflows as named commands that Claude executes consistently — every time, without drift. [1] Commands live in .claude/commands/ at your project root, or ~/.claude/commands/ for global commands. Each command is a markdown file: the filename becomes the command name, and the content is the instruction set Claude follows.
A file at .claude/commands/review-pr.md becomes /project:review-pr in your Claude Code session.
/project:test-and-fix process, you get predictable, auditable behavior instead of improvised solutions. This matters most in agentic workflows..claude/commands/ directory in version control; it's engineering infrastructure nowFor more on building durable Claude Code workflows, see my best workflow for working with Claude Code.
Once CLAUDE.md and MCP servers are in place, the next level is orchestrating multiple Claude Code instances as specialized agents that hand work off to each other. The most reliable pattern is one orchestrator instance that plans and delegates, paired with specialized subagents that execute. [1]
In the Buddy Google Ads agent specifically, this pattern runs as: a planning agent that interprets campaign performance data and decides what optimizations to propose, an implementation agent that writes the API calls [4], and a validation agent that checks proposed changes against account rules before anything reaches a human approval queue.
Context window management is the other common failure mode. Each agent in a long chain accumulates context, and without active management you'll hit limits or get degraded outputs. The practical fix: summarize outputs before passing them forward. Don't pass 2,000 tokens of test output to the next agent — pass a 200-token structured summary with the full output stored to a file the agent can reference if needed.
For more on dynamic handoff patterns, see dynamic workflows in Claude Code.
Claude Code V2 configured this way isn't only a developer tool — it's infrastructure for building the custom AI tooling that marketing campaigns actually need. Generic AI tools are built for median use cases. Your Google Ads account structure, your creative testing methodology, your attribution model — none of that is median.
A marketing technologist or technical account manager with this setup can build:
The CLAUDE.md for a marketing-focused project should include your attribution model, your KPI hierarchy (ROAS, CPA, impression share — whichever drives decisions), your account structure conventions, and references to the platform API documentation your agents will need. [4] MCP servers like a Google Ads API integration or a custom reporting database connector become your agent's data access layer.
If you're exploring what production advertising agents look like end-to-end, getting started with Buddy walks through a real example built on exactly this stack.
.claude/commands/ directory, and your MCP configuration should all live in your repo, be reviewed like code, and evolve deliberately alongside the project.There is no fixed limit, but production CLAUDE.md files typically run 300–600 words. The goal is structured information Claude can parse quickly, not comprehensive documentation. If a section wouldn't change how Claude behaves in a session, it probably doesn't belong in the file. Err on the side of shorter and accurate over longer and aspirational.
MCP servers themselves don't directly add to Claude API costs — they're external processes that supply information. However, the data they return (fetched documentation, search results, file contents) gets added to your context window, which does consume tokens. In agentic workflows where token costs matter, this is worth tracking and is exactly why a "cost-estimate" custom command is worth building early.
Yes. Commands placed in ~/.claude/commands/ are available globally across all your Claude Code projects. Commands in .claude/commands/ at the project root are project-specific. A practical approach is to keep generic commands (security checks, changelog generation) global, and keep project-specific workflow commands (API audits, agent-specific steps) local to the repo.
The most reliable approach is layered constraints: encode the agent's boundaries explicitly in its CLAUDE.md context, design MCP server access so it only has the permissions it needs (a reviewer agent shouldn't have GitHub write access), and define human-in-the-loop triggers as a named list in the agent's instructions. Constraints that live only in workflow design — not in context — tend to erode over long sessions.
A technical marketing manager or marketing technologist comfortable with code editors can absolutely use Claude Code V2 effectively. The CLAUDE.md and custom command setup does require some initial configuration, but once in place the day-to-day experience is closer to directing an engineer than writing code. For purely non-technical users, a purpose-built agent interface is likely a better starting point than raw Claude Code.
The "Current Sprint / Active Context" section should be updated weekly at minimum — it has the highest decay rate. Tech stack and convention sections change less often but should be reviewed at the start of any new project phase. A practical habit: make updating CLAUDE.md part of your sprint planning or weekly review, the same way you'd update a README after a significant architectural decision.
More answers in this topic: Claude & Anthropic