User
Write something
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
6227 members have voted
Pinned
🚨 You've been asking when the Lyceum opens. The waitlist is live. 🚨
The waitlist is up and seats are limited, so this is your nudge to go lock yours in. 👇 New here? Quick context. 👀 The Lyceum is Jake's live cohort program built on ICM, the methodology 35,000 people in this community are already using to get real results with AI. The short version: folders over agents. You learn the layer underneath the tools, the one that keeps working when the next model drops. Full breakdown is on the site. Here's what's inside: 🎯 Three cohorts, Technical, Business, and Creator. Same methodology, built around what you actually do. 🎥 Live sessions with Jake and a full team of instructors. ♾️ Lifetime recordings, written curriculum, and a private cohort Discord. 📜 An Eduba ICM certification you can put on your resume. And a guarantee no course makes: ✅ You leave with a working product, or the team finishes it with you. ⏳ Seats are limited and this community moves fast, so the math is not in your favor if you wait. 💡 Pricing and start dates aren't public yet. The waitlist sees them first, gives feedback on timing, and gets in before the program opens. Everything you want to know is on the page. If you already know this is for you, get on it. 🔥 👉 https://lyceum.eduba.io
Pinned
⚠️ HEADS UP: PHISHING ATTEMPTS IN THE COMMUNITY ⚠️
We've noticed people sending out phishing links in DMs and comments. Quick PSA to keep everyone safe. ---- 🛑 THE RULE If someone you don't recognize is sending you links, asking for money, asking for login info, or telling you to "claim a prize" outside of an official competition post, it's not us. Don't click. Don't reply. Just delete. ---- 💰 HOW WE ACTUALLY HANDLE MONEY We will never send you money out of the blue. The only time you'll hear from us about money is if you've won a competition. When that happens, Sonija is the only person on our team who will reach out to collect your payment info to send your prize. If anyone else DMs you asking for payment details, banking info, or "verification" to release a prize, it's not us. Report it!! ---- 🚨 IF YOU GET A SUSPICIOUS MESSAGE 1. Don't click any links 2. Don't reply 3. Screenshot it if you can 4. Send the screenshot to Jake, Matt, or a mod so we can deal with it We're going to keep this community a safe place to build and learn. Thanks for looking out for each other. 🙏
📑My Read on the weekly comps: what's crucial, what changes, and where the context.md fits
⭐ I am waiting on some feedback on this, I could be off with my read, I am willing to be wrong in public so we can all be right when we are building in private! The rules feel like they contradict each other week to week. They don't. 📍 WEEK 6 AT A GLANCE — THE RESEARCHER https://www.skool.com/cliefnotes/weekly-comp-6-the-researcher?p=fa674d82 🔬 Build: a single folder-based AI researcher for ONE specific domain (you pick). Five files, single folder — so no handoff.md and no context.md this week. 🚫 The angle: a researcher is NOT a summarizer. It asks what's missing, questions the framing, weighs sources by credibility, and asks clarifying questions before it produces. That lives in rules.md ⚖️ New wrinkle this week: judging adds "does it weigh sources / flag uncertainty?" — bake that into rules.md. 📨 Submit: public GitHub repo + 2-3 sentences on what your researcher covers and what work it's best for. 🎟️ Prize: a free Lyceum seat (pick cohort — Technical / Business / Creator). 📅 Due: Sunday, May 31, 12:00 PM EST (shifted for Memorial Day). Winner Mon June 1. Premium + VIP only. 👇—My Take Below! How the rules have read to me since my first entry and getting a bit of clarity🔮 💡There's a spine that never moves and a set of dials that change every Sunday. Once you can tell those apart, the whole thing gets a lot less stressful. ⚠️This is the post I wish I'd had before I submitted, hopefully it brings clarity to an awesome community opportunity! These competitions are like mini boot camps, the tools you take away compound. 🧩 One part to focus on is the use of: context.md 📑The lessons teach ICM with a context.md in basically every directory. Then the comp spec lists five files identity.md, rules.md, example.md, reference/, README.md, and context.md is nowhere. 🤔 So, you sit there wondering if the spec is wrong, or if you're supposed to "know better" and add it. ⚠️ Here's how I am seeing it fits. context.md is a routing file. Its whole job is navigation: in a multi-directory system, it tells the AI what lives in a given directory and where to find it. It earns its place when there's enough material that the AI would otherwise waste effort hunting.
Big Win! Using ICM Cut my co-worker's manual task from 2 days to a few minutes and getting an upgrade to Max
TLDR: My co-worker has been manually extracting data from 100s of files one at a time and manually managing files for years. This is a longterm client with set workflow. Usually takes him 2 days and I set up a workflow that will do it in a few minutes. Showed my boss and CEO and got the ok to get a Claude MAX seat. Context: I'm a sound designer and work at a post-production audio studio that also does games. The post engineers work on a lot of projects that require manual setup. They were griping at lunch about how they have to open hundreds of text files to find 1 single line of data that they need during their edit session and then manually qa it against the session when it's setup. It sounded like hell to me so I asked if they wouldn't mind showing me what they have to do and they literally manually open each folder, find the text file, write down on a piece of paper the number and then enter it by hand in the computer later. I spent 10 minutes and described to claude what I needed a python file to do. It gave it back to me and the script was able to extract the data they needed in seconds. But that got me thinking, I know there's a python library that works with Pro Tools (our audio editing software), and the current weekly contest is about making a specialist... COuld I make a specialist in Protools Python scripting that can tailor workflows to any engineer? So I spent about 4 hours speccing an ICM folder that specializes in Python Scripting for Pro Tools. Brought it to work today and --- it didn't work -- immediately at least. IN practice discovered there were errors in the documentation for the python library, so we had to fix the documentation. But after that was able to create a contained python script anybody could run and showed my co-workers and ceo. They were super excited about the possibilities and when I asked if I could go ahead and get a Claude Max subscription they said yes immediately. Might also be showing the wider company the setup and what's possible next Monday. Was totally worth staying up all night yesterday to get this out 🤣
1-30 of 1,442
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by