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
6820 members have voted
Pinned
14h •
Calling all friends, asking for your support if you can spare it ❤️
My best friend’s dad is currently going through cancer treatment and there is a go fund me to support his medical costs. I’m not expecting anyone to contribute life is costly enough but if you have it in your heart and are able to help it would be appreciated more than anything. Thanks in advance to anyone who takes the time to read this! https://www.gofundme.com/f/support-mikes-cancer-journey-594gk?attribution_id=sl:15012345-d96b-4d61-8d72-478b304a6fae&lang=en_US&ts=1781827434&utm_campaign=fp_sharesheet&utm_content=amp20_t1&utm_medium=customer&utm_source=facebook&fbclid=IwRlRTSASheIRleHRuA2FlbQIxMQBzcnRjBmFwcF9pZAo2NjI4NTY4Mzc5AAEewEgvL9AJQEZZj4hn-1GjsoRFFucAjFoNIwMfSrKK0H6msk7Hga8rGkqyWWg_aem_sJu0t4KDXFlHZ4Z_eAyFbA
Pinned
👑
⭐
16h •
WEEK 7 COMP⚙️ THE OPERATOR — RESULTS
(and a small change to how we run these) Hello everyone!! 👋 First, the honest bit. This one is landing later than Monday, and on purpose. Two things got us here. One, a lot more of you are submitting now. If I am going to really sit with every entry and give it a proper look, a weekend is not enough. This round I went through all of them, watched the videos, opened the repos, the full pass. That takes time and I would rather do it right than rush it. Two, I could feel a few of you running hot. Weekly is a sprint, and burnout was starting to creep in for some. So we are moving to bi-weekly. More room to build, more room to breathe, and the time for me to actually review the work the way it deserves. 🎥 Quick word on the videos. They were a step up this round. Some of the animated walkthroughs and live demos were a genuine pleasure to watch, and yes, I weigh them. A clean demo that shows the thing actually working makes a real difference. However I don't want that to ALWAYS be a requirement. Also you will notice the Heavy hitters that you usually see up here are not currently, some posted late and I decided to let the new entries and first timers also have a chance as well! But certainly, check the original post as every submission has something for you to learn from : 💰 Competition 7 ➖➖➖ 🛠️ A FEW THAT STOOD OUT (in no order, and if you didn't make it, it doesn't mean yours wasn't great) The Pipeline Operator — @Jayden Forshee Runs a whole sales pipeline. Paste a lead and it grades it, writes the outreach, and moves the card itself. The live board where you watch cards move on their own, sat right next to a normal chatbot, was one of the clearest ways anyone has shown what an operator actually is. https://github.com/griffainai/studio-pipeline-operator Board: https://pipeline-operator.vercel.app/board
10h •
Thank You for the Win - It is a Win because of You
I keep coming back to one thing today: I didn't build any of this alone. Thank you, genuinely, to this community. Winning Week 7 is humbling. But the part I actually want to mark is what it took to get here, and how much of it came from you. Over these weeks I've sat with the repos people shared in here. The pipelines, the auditors, the intake operators, the safety checkers. I opened them, read how they think, and walked away a better builder every time. Honestly, half of what's good in my own work started as something I noticed in someone else's. That's the quiet gift of this room: everyone's work is a lesson, if you're willing to look. To everyone who read my articles and clicked into my repos, and especially anyone who left a comment: thank you. You may not know what it means to put something out and have a person actually see it. After thirty years of teaching, that still lands every single time. And to the team I built that operate behind the scenes who put in the hours so these builds could ship clean: I see you. This one is yours too. I'm not going anywhere. I want to keep sharing what I'm learning, and just as much, keep showing up for your work the way you've shown up for mine. Grateful. Let's keep building. 🙏 — Gabe Oh, and of course @Jake Van Clief and the entire back team that supports us - without you, none of this would have ever been possible in my life. Words do very little to truly honor and express my gratitude for this recoognition. And now...for the virtual champagne bottle opening 🥳🥳🥳🥳🥳🥳🥳
1m •
A simple operational summary of ICM with a “video to study PDF” example
I made a small personal operational summary of Jake’s ICM paper while studying it. It helped me clarify the core structure in a more practical way: layers, stages, workspace structure, how outputs move from one stage to the next, and how the “factory vs product” idea works in practice. I also included a simple hypothetical “video to study PDF” workspace, which is the kind of workflow I’m using to understand how ICM can help turn technical videos into structured study notes. The summary explains how one stage produces an output, how the next stage reads that output as working material, and how the stage’s CONTEXT.md defines which files and references should be used. It’s not official material, just my own study notes, but I’m sharing it here in case it can help someone else who is trying to understand ICM more operationally. Happy to improve it if anything is unclear or inaccurate. stay curious 🫡
0
0
1-30 of 1,922
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
🔥
+2019
2
+1623
3
+1265
4
+603
5
+502
Powered by