@pro.glitch: How to build an AI team in Claude Code — every step One AI employee is Claude Code plus three things on its desk: a job description it reads every time it wakes up, playbooks for the jobs it owns, and a notebook where its lessons go. Build that five times and you have five strangers. The team is everything you add on top. Here is the whole build, in order. 1. A desk for every employee. Each one is its own folder: job description, playbooks, notebook, working files. Nothing leaks between desks, so one glance tells you what each employee knows and owns. 2. The company folder. Three pages every employee reads the second it wakes up: one about you (how you work, what always waits for your yes), one on how the company talks, and the roster with a one-line job for each employee. Write your brand voice once and the hire you make on Friday inherits it on Friday. 3. The shared notebook. Corrections that belong to everyone (a brand rule, a platform policy, a tool nobody touches without asking) go in one notebook the whole team reads. Correct one employee Tuesday, all of them follow it Wednesday. 4. Handoffs. When a job shows up, Claude Code reads the roster one-liners and passes it to the right employee. Employees pass work down the line themselves: spin up a teammate in the background, wait for an answer, or leave a note in a teammate's inbox. You are out of the middle. 5. One board. To do, doing, done. Every employee moves its own cards and submits finished work for your review. One screen tells you who is on what. 6. A clock on every desk. One employee sorts the inbox at nine, another leaves you a trend brief each morning, another checks for approvals every half hour. The team has been at work for two hours before you wake up. 7. Fences. Each employee gets an enforced list of what it can touch (leave writing off the list and it physically cannot write a file) and a short list of what always waits for your yes: sending outside the company, spending money, deleting anything. 8. One employee whose whole job is hiring the others. Say what you need, answer three questions, and a new hire is on the roster and online in your dashboard a few minutes later. The rest of the team knows it exists before you've said a word. How it all moves, for anyone who has never written code: underneath the team sits a set of scripts. A script is a small piece of code that does one chore the same way every time. One builds a new hire's desk and adds the roster line. One carries messages between employees. One wakes each employee on its clock. One files a new playbook onto the right desk. You never open them. They fire when the moment comes. A worker runs a job. A team runs the company. This is how my own operation runs: Quill sorts the inbox, Nova reads the trends, Atlas writes the proposals, Rack keeps the servers alive, all from one shared company folder, one notebook, one board. If context, skills and notebooks are still new words to you, that's who this is for. Seven courses inside my community take you from knowing nothing to building this, in order. The platform itself, the exact code my employees run on, every one of those scripts included, is in there too: download it, open it, start hiring. Join us and start today. The link is in my profile. #aiemployee #aiagent

Professor Glitch

Open In TikTok:

Region: US

Sunday 13 September 2026 12:24:56 GMT