Every agent that writes for you needs the same context.
How you talk. Your stories. Your customers. Your offers. Your design system.
That's 6 plain text files.
Keep them portable, in one central place. Switch between Claude, ChatGPT, Grok Bot, Hermes or Muse, and they're all playing from the same sheet of music.
I run 3 companies. Each one runs on different systems.
One is in the middle of a full product launch. The team runs it on Monday (the PM platform)
I hate logging into Monday. When I handed over operations to that company, I figured I'd never have to again.
Then I came back to help coordinate the launch, and I was dreading it. Digging through tasks. Hunting for links to docs. Three logins to three different tools.
So I didn't.
Here's the philosophy:
1. Know what you love doing.
2. Know what you hate doing.
3. Offload as much as you can of the stuff you hate with agents.
4. Simplify how you handle the work that only you can do.
Project management is a necessary evil when you work with a team, human or AI. But if you don't want to log into Monday, then don't. Have your agent work in it for you.
Grok Bot used Claude to build me my own Kanban board. It replaces Todoist, Monday, ClickUp, etc.. Personal and business tasks live in one place. I assign tasks to agents from that board. When something gets done, by me or an agent, it updates everywhere.
One board. My agents manage the chaos.
Just tell Grok Bot, Hermes, or whatever you're using...
"Yo, here's what I enjoy doing, here's what I hate doing, here's the list of tools I use, what can you do to help make my life simple?"
Your agents need two kinds of knowledge files to do good work:
1. General business knowledge. Every agent needs it.
2. Specialized knowledge. It depends on the role and the job.
The first takes one interview and gives you the 6 essential files. Every agent's output gets better on day 1.
The second is role-specific: frameworks, samples, workflows and runbooks.
@Michael_Fenech_ The bot-to-bot communication was our biggest usage problem.
After adding rules for agent communication, usage dropped significantly from close to 40% to below 20% of total.
@datachad Agreed. I have role-specific rules for each specialist agent. Visual rules for graphics, writing rules for content & copy, etc. The 6 are more general knowledge. The others are "per agent" rules, so agents review against them before the draft arrives.
@lukepierceops $5K for one workflow with approve steps is sane.
I still won't let an agent publish without me reading it first. Learned that the hard way.
@coreyganim The Notion log is legit. We keep a draft.md and a status.md on every piece of work so the client (or me) can see what actually shipped without asking the agent.
The AOA order matches how I used to onboard contractors: write the process, cut the junk, then hand it off.
@GrokBotRadar 13 for me. 6 do the bulk of the daily work. 3 are more supportive but still essential (backend engineer, research, metrics). The remaining are sorta on standby for near-term projects.
My AI team peaked at 13 agents.
One had the new offer, one had last year's voice guide. I was the intern carrying notes between them.
I run three companies. One did over $5M last year without me running it day to day. Another is on track for 7 figures. My personal brand is just me and my agents (zero team members).
Those business results aren't agent results. Adding agents still left me copying information between chats.
Keep the current business knowledge in one shared folder. Then give each agent instructions for its role and tell it which files to read before starting.
The six starter files and setup:
Give audience.md a customer you can picture.
Illustrative, not a real quote:
Before: "Busy professionals who want growth."
After: "I need next week's emails done without spending Sunday rewriting them."
Save real customer language. Template:
Save corrections in the relevant guide and published work in the archive. Keep the folder outside the AI tool. Give the next agent access before it starts.
Copy all six templates and the setup prompt:
Everybody's building AI agents. Most of those agents don't know what the business sells. Here are the 6 files mine read before they're allowed to touch anything:
Build the knowledge first, the agents second.
visual-brand-guide.md: Colors, fonts, logo rules, screenshot standards, and what to avoid.
Save specific rules and approved examples. 'Make it look good' gives the agent plenty of room to make something you hate.