User
Write something
Afternoon Tea is happening in 4 days
Pinned
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
5085 members have voted
Pinned
🏆 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
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
AI doesn’t make coding irrelevant. It makes coding more accessible.
Here’s something that’s been sitting on my mind. We’re in a moment where a lot of people are saying learning to code is no longer necessary. That AI can just write the code for you. And on the surface, that argument sounds reasonable. But I think it misses something fundamental about how software actually works. The abstraction stack has always looked like this: Natural Language → [AI translates] → High-Level Code (Python, JS) → [compiler] → Assembly → [CPU] → Machine Language This is the same pattern software has always followed. We went from punching machine code, to assembly, to C, to Python. Every layer up was an abstraction that made the layer below more accessible. AI is simply the next one. You can now describe intent in plain English and get working code back. That’s powerful. That’s genuinely a shift. But here’s what hasn’t changed: The AI still produces code. That code still runs on software engineering principles, and neglecting those principles is just like pushing code that’s never been vetted. Same same, but different. If you can’t read what it produces, you can’t evaluate it, debug it, extend it, or know when it’s wrong. Think about it you wouldn’t trust a translator if you had no idea what language they were translating into. Same logic applies here. And here’s the honest truth: learning a programming language alone isn’t enough right now, because AI is doing that part better by the day. What actually matters is the engineering fundamentals. They teach you how to think in terms of logic, data flow, state, and structure. Those aren’t things AI removes from the equation they’re the things that help you direct AI well. So do we still need to learn to code? My take: software engineering fundamentals are non-negotiable. Understanding how code works, what a function does, what an API call is, how data moves through a system these matter more now, not less. You need to be a good reviewer of AI output. And knowing the fundamentals lets you govern what AI writes and how it writes it throughout the entire development process.
Anyone using Gemini (when you out of tokens)
Are you using desktop or browser? both? Free or a paid version? What have you used it for? I’ll go first….
1-30 of 1,117
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by