Decided to put some faces and names behind my agents after about 4 weeks in my folder structure. I'm about 3000 files deep and 300mb of markdown and text files. I've still only onboarded about half my clients into the system. I needed a way to visualize what had been built already and where my orchestrator was sending tasks. About half the agents have soul.md built into their instructions as well. This has been a fun project. https://collideascope.co/team/ai-team-roster.html Curious if anyone else has done anything similar.

Twenty-four days ago I posted about Jake's folder system video. This is what happened next. Same foundation — markdown files, orchestration prompts, clear roles. I just kept building. Fifteen named specialists. Each one with a soul file, guardrails, and a playbook. Duke orchestrates. Cash writes. Trace pulls the data. Hank runs the financials. Clint handles the MCP integrations. Behind each one is either a human counterpart doing the real work alongside them — or a role I can't afford to hire yet. Katie who's been with me for 18 years, now has her own orchestrator running the same system. Twenty-seven client folders. Twelve live MCP integrations. One shared repo. The folder system isn't replacing my agency. It becoming my agency. Jake gave me the unlock. This is how it's going.

There have been some good questions in my previous posts about my agents, so I want to clear up a few things. I call them agents because it helps me think and stay organized. But strip the jargon and here's what's actually happening: a folder with the right files in it tells an AI who it is, what it does, and what good looks like. Unix figured this out a long time ago. I remember working on mainframes in my early 20s. Files in folders. It wasn't powerful because it was complex. It was powerful because it wasn't. Unix came out in 1969; I was using it from 1998 to 2002. The "writing room" is a folder. Cash lives in it. His instructions, his guardrails, his examples, his voice reference — all files. The AI reads the folder and knows how to behave. The room gives it context. The files give it structure. I have 15 of these rooms. Duke orchestrates between them. The naming isn't the point. The structure is. Here's the part most people miss: almost every agent in my system has a human counterpart. A real expert whose domain knowledge shaped the instructions — and who can tell me when the agent gets it wrong. Cash's counterpart knows copywriting. Trace's counterpart knows data. That feedback loop is how the system actually improves. You're not building AI. You're building infrastructure. Build the foundation. Build the structure. The agents are just what you call it when the rooms start working together. My lesson: don't copy me, don't copy Jake, we all learn from each other, and then you make it your own. Stick to the fundamentals. Watch Jake's videos; it will rewire your brain and change how you think about AI. There are no shortcuts. You have to build a foundation first. Links to referenced posts: https://www.skool.com/quantum-quill-lyceum-1116/visualized-my-agent-team https://www.skool.com/quantum-quill-lyceum-1116/the-folder-system-became-my-agency

I'm curious what everyone here likes to do for fun (of course building stuff with Claude is fun too lol), and if you've applied any AI to your hobby. For me it's been super useful for DND planning and I find I get to stay in creative flow more. Curious what other people are doing

Here's how we build new pages for client's now. Takes about 25% less time. First: an interview. We get the client on a call, follow a structured intake, get everything we need. Claude ingests the transcript and maps the requirements — buyer, intent, conversion action, messaging priorities. That's the foundation. Then Cash, our copywriter agent, writes the copy. Then Ruby, our front-end designer, takes the copy and the client's identity system and builds a clean HTML/CSS mockup. We hand it to the client. They give us feedback. We collect assets — photos, logos, screenshots. Then Cody. Cody has access to the Elementor JSON templates our human designer originally built for this client's site. He reads the approved HTML. He generates a new JSON file in the same structure — same design system, same component logic, same brand patterns. We import that JSON into Elementor. The page is 90% built. The humans still do the review. The humans built the original templates. The humans ran the interview. But the production time? It collapsed. Jake's folder system didn't replace the agency. It restructured where the human work actually lives.