Pinned
Mar 15 •
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
5078 members have voted
Pinned
13h •
🏆 WEEKLY COMP #4: THE AGENCY 🏆
💰 $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.
Pinned
👑
⭐
6d •
I come asking for help! (NEW ROUND! VOTE ONCE A DAY PLS)
Because of the Amazing support you all gave for the first Round Wylder (my step daughter) made it into the second round! You can vote once a day and some days are 2x votes ! I would love love love if any of you support her going to work with some of the best animal rescues in the world to just cast at least one free vote if you can! You can vote here! Not Ai related so sorry for that ! Wylder | Junior Ranger
4h •
How does memory work with the folder system
Greettings everyone. Pepe here from Santiago, Chile. I've followed the basics of folder structure and it really makes sense. But i've got some issues. How the system records what i do? Could i do something in order to get memory? I've watched some advanced videos about making an OS System and i get that that woould be overkill on my current state: i'm just becoming an AI Freelancer that wants to make it. In order to do that, i would like to have a content lab and maybe some way in with the whole system records my actions. My first impression is that every folder should record his own, like in order to make content, the draft folder maybe resolves this issue. Is a memory layer to get what we do everyday overkill? Does anyone uses something like this? How can this be done respecting the folder structure? If you have an idea how to make this. I'd really apreciate some advice. Thanks a lot!
24h •
Stop using MCP's ... mostly
OK, maybe not all of them, but for the most part you should be able to eliminate 90% I stumbled across this old blog post from the creator of PI AI (https://pi.dev/) and it's genius. It shows you how to easily remove the common web browser MCP's and replace with code. WHY ? - Because when you run executable code you no longer need to use the complex MCP queries which are typically bloat for all use cases, it simply runs the code. 1 line. What You need, not what 1million users need. Unfortunately it was about a week late, I could have used this a week ago as I was having trouble scraping epic-games for Unreal Engine documentation. I tried a number of different scrapers, Skill-Seekers, one I built for SEO about 5 months ago... and then decided to use Firecrawl, however I had to pay for it as it's over 6000 pages. So $36 later... THE BLOG POST: https://mariozechner.at/posts/2025-11-02-what-if-you-dont-need-mcp/ having 4-6 MCP's connected really adds some overhead. I even noticed this issue with Codex, I had to uninstall Vercel (3x bigger than GitHub), and a bunch of others. So moral of the story, keep your MCP's very light, if any at all. Even the GitHub MCP is pretty much pointless unless you're doing heavy actions / worktrees. Using 5 agents on 5 different trees. etc. If you're just doing light Push.Pull.Merge.Commits. then you don't need GitHub MCP. And after reading this post you can safely get rid of Playwright, Puppeteer, Chrome MCP Browser tools etc. All scripts can be downloaded here: https://github.com/badlogic/browser-tools
1-30 of 1,115
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
1
+855
2
+815
3
+764
4
+635
5
+430
Powered by