I just found this prompt while doom scrolling instagram: "Help me set up permissions using /permissions. I want to pre-approve three things: Safe commands so Claude doesn't stop to ask every time: Is, cd, mv, cp, cat, and open Reading files in my working folder without asking Fetching safe webpages without asking Walk me through each one." I ran it in claude code (using vs code, but I don't think it matters). It just did it and wrote to the ~/.claude/settings.json file, so that claude can now continue to build less interuptions! I hope I didn't just unleash a beast or anything....

💰 $325 CASH 💰 That's a full year of Premium. Win this and your membership pays for itself. But the real prize this week isn't the cash. Keep reading. 📋 THE CHALLENGE You just got hired again. Meet Diana, owner of a 4-person boutique real estate team in Austin. 60-80 transactions a year, mostly residential, mix of buyers and sellers. 📎 Download the full client brief attached to this post. Short version: She doesn't want software. She wants a system she can teach her team to use in a week. Your job is to build the AI operating system for her team. This isn't one specialist. This is a small team of AI specialists organized into a multi-folder ICM architecture, with a clear handoff protocol between them. 🗂️ WHAT YOU'RE BUILDING Last week was one specialist. This week is a team of them. Required folders: 📍 00_orchestrator/ — The router. Where every request starts. Decides which specialist gets the job. 📍 01_lead_qualifier/ — First contact with new prospects. Captures intent, budget, timeline. 📍 02_property_research/ — Deep research on specific properties or neighborhoods. 📍 03_client_communication/ — Drafts emails, texts, follow-ups in the voice of the agent. 📍 04_transaction_coordinator/ — Handles the deal once it's live. Checklists, deadlines, document tracking. Each folder must include: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 🔗 handoff.md (NEW for Week 4 — how does this folder pass work to another folder?) - Plus a root-level README.md explaining the architecture, the typical flow, and how to onboard a new team member. 🔥 WHY THIS ONE IS DIFFERENT Weeks 1, 2, and 3 were warmups. This is the comp where the work you ship genuinely starts to look like the real thing. The handoff protocol is the test. Anyone can build five folders. The hard part is defining what each one needs from the previous one and what it passes to the next one. That's where multi-agent systems actually live or die.

💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.

background: SO, I've been in this community for about 3-4 weeks now. I started getting deep into Claude a few months ago, and build a web app game, and a sales pipeline for it. every post on my instagram feed became some hype merchant trying to draw you in with some impressive and not realistic way that they were using claude. Then I saw a post from Jake about folder structure, and I thought "my Ai usage is a mess, anything that can help me systemise it is great". I still didn't know what Jake was actually offering, but he wasn't hyping it up, just talking real. So i jumped into this 'course' and started at the beginning. Straight away, I got so much value from really understanding what Ai actually is! I finished the first 2 modules, and then Jake put up a 5th May sale, which just made the premium pricing totally worth it! I jumped on board, mostly because I had already gotten so much value from the free content. but then before I even dove into the next level of content, my brain had a slight shift. I suddenly saw this place for what it was; a community! it became a place to not only get, but to give back. my comments on other peoples posts went up and my general interactions with the community. Now, you don't need to pay to become a part of the community, but for me, that created the biggest mindset shift. probably in a few weeks I would have got it anyway. so, thus far, that has been the biggest piece that I have 'gotten' from upgrading to premium... a mindset shift to actually invest into this community!

Five agents. 160 hours down to 5 minutes. $7,500/month against a $39K-$59K traditional team. And the AI? Maybe 20 lines per agent. This lesson breaks open a real system I built for a mining compliance client in the DRC. Every component mapped to the ratio. Every pricing decision shaped by the architecture. The course companion has five exercises you run with Claude using your own work. Not hypotheticals. Your actual systems. Your actual pricing questions. If you've gone through it, which exercise hit hardest? 👇