From Basic AI Prompts to Agents, MCP, and a Builder Stack I Never Needed at Work

A few weeks ago I was prompting Claude to draft a brief for the third time that day. Same brand context. Same audience constraints. Same three guardrails. I caught myself retyping a paragraph I had retyped fifty times that quarter. That was the night I stopped prompting and started building.

A year ago my AI workflow was: open a chat, paste context, hope.

Today it includes daily routines, lightweight agents, skills, MCP connections, and a growing list of dev tools I had heard about for years but never had to operate myself.

None of this replaced my marketing career. It extended it. Into places enterprise teams talk about but rarely let non-engineers touch.

Where I started: prompts

Prompts taught me AI could draft and summarize. They also taught me the ceiling: without structure, every session starts from zero. Every brief re-explained, every brand voice re-described, every QA checklist re-typed.

What changed first: systems

The jump was storing how I work. Reusable skill files. Project context that survives across sessions. Checklists for brand voice and handoff and QA. This is where quality became repeatable instead of lucky.

The first one I wrote was a brand-voice file that catches every time I drift into consultant cadence. Bulleted lists where the work calls for sentences. Words like "leverage" that sneak in when I am tired. Now Claude flags those patterns before I do.

What changed next: agents

"Agent" is an overloaded word. For me it means a defined job, a trigger, and guardrails. A research routine that runs every Monday morning. A triage agent that reads my inbox and flags the three messages worth opening first. A draft assistant that knows my style and runs on schedule.

I am building these the way I would design a campaign ops rhythm. Not autonomous magic, but reliable assistance with clear ownership.

The first one I wired up is a Monday morning research routine. It pulls the previous week of competitor and industry blog posts in my space, ranks them by relevance to our current programs, and drops three bullet points into my Notion daily note before I open my inbox. The first week it missed context I cared about. By week three it knew which adjacencies mattered and which did not. The fix was not better prompts. It was a tighter source list.

What changed most: MCP

MCP (Model Context Protocol) clicked when I stopped thinking chat window and started thinking plug-ins for context. Pull from the right source. Act in the right system. Return something verifiable.

It is the difference between AI that guesses about your repo and AI that can work with your repo.

The first MCP connection I wired up was Claude to my Notion workspace. Now when I ask "what does our current strategy doc say about X," it reads the live page. Not a stale paste. Not a summary I had to assemble. The first week I caught it pulling from an outdated draft I had forgotten to archive. I fixed the source. The next week it stopped guessing.

The stack I learned without being "a developer"

Here is the honest list. Many names I knew from slides, few I had operated until recent weeks.

| Tool | What I knew before | What I know now | |---|---|---| | GitHub | repos exist | branches, commits, PRs as shipping rhythm | | Vercel | "hosting for Next" | deploy previews, env vars, production flow | | Netlify | alternative host | static deploys, simple pipelines | | Supabase | "Postgres in the cloud" | auth, tables, real backend for side projects | | Cursor | nothing | primary build environment | | Copilot | autocomplete hype | useful inside established codebases | | ElevenLabs | voice AI demos | audio prototypes for concepts | | LiveKit | real-time video infra | learned while exploring live product ideas | | MAMP | local PHP stack nostalgia | local environment mental model |

I am not claiming expert depth on all of these. I am claiming something more useful to my profile: I can orient, configure, and ship with them without waiting for a engineering ticket.

What changed in my head

I stopped asking, "Am I allowed to build?"

I started asking:

• What is the smallest verifiable slice?
• Which tool owns which job?
• What should remain human-only?
• What is worth automating vs. worth feeling?

That is a marketing leader's framing applied to a builder's toolchain.

Where this goes next

The next layer is not more tools. It is better governance. Clearer agent boundaries. Better logging of what changed. Tighter loops between insight and ship.

I am still a marketer. I just refuse to be one who can only work in decks.