User
Write something
New Member Onboarding. is happening in 11 hours
Pinned
Welcome to Clief Notes. Here's where to start.
1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. 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 join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?
Pinned
📢 Recordings of Tea Masterminds are live: The Second Brain
🧠 This round was about what a second brain actually is: a context layer you and your AI both read, not a notes app. The Afternoon Tea is the teaching. The High Tea is the room putting it to work on scale, memory, trust, and security. Here is what I want you to understand about these drops, because it is the whole point of being in here. While the videos are valuable and being able to sit and answer your questions is a big reason for them that's not the only value they hold. 📄 Every drop is a set of working files. Markdown built to be used and reused. Each one ends with the exact data to give your AI for your own situation. This round also ships a starter folder you can open, run the self-audit on, and walk away with the skeleton of your own second brain in a sitting. 🤖 I build them expecting you to feed them to your AI. That is the design. Hand a whole round to Claude in a few minutes, whether or not you made it live. The room's thinking is in the files, so you lose almost nothing by catching it later. 🔄 They adapt. A prompt pack is frozen. These are meant to be reshaped: update the context, swap in your own work, bend the templates to your process. And they grow on my side too, as we learn together in these calls. The call is dialogue. The package is that dialogue, crystallized into something you can run. Next round builds on this one. ☕ Afternoon Tea 6 →Afternoon Tea 6 (Second Brain Chat) 🫖 High Tea 10 → High Tea 10 (Second Brain Deep Dive) 🧭 How you should use these: 🔹 Show up live when you can. Your questions shape the next drop. 🔹 When you can't, rewatch, or drop the files into your AI and run the prompt at the bottom. 🔹 Open the starter folder and build your own version. Rename it to your work. It is yours to keep. 📚 A mastermind ends when the call ends. What you get here keeps working after: a structured version of your own thinking (and some of my own thinking!) that improves every round. In my opinion that is worth more than the hour in the room. (or three as some of you stick around in these calls to chat)
Pinned
Ai before ChatGPT: The Interview.
In this interview I sit down with Matt from NLP Logix. He's been working in the AI space longer than most people have been working in general. We dive into what changed and what is it going to be important about the future. This is a three part series, I will be posting another two videos from another two experts in mathematics and Engineering! Please like and comment on YouTube if you have time as well!
File system access across devices
TL;DR How can I build my folder/file system so that it can be accessed and used across devices? I am always on the go, sometimes working from my phone, sometimes my laptop, sometimes my husbands laptop, sometimes my desktop. I'm looking for a central hub to store my files on that will sync across devices. Is anyone already doing this? I've been using Obsidian Sync with a backup to GitHub but since I want to be able to use Jake's ICM system with the third layer of files and artifacts, Obsidian doesn't seem to be working great for that. Is anyone building their whole knowledge base right on GitHub or using a different cloud solution?
Fable to Opus Flagging - Quick prompt caveat to get Fable working where it can
This is a quick note to add to any instruction to ensure that Fable naturally finds it's own existence guardrails iteratively (with human in the loop) while it can - it's a quick "defog of war" method to see what can and can't be seen by Fable that's working for me so far. Run it a few times deeper and deeper and send your final Fable task into the guardrailed system. "If you run into anything that triggers a model switch from fable to opus, flag it, suggest operating pattern to avoid it on the next run, and notify me so that I can restart it with that rule."
1-30 of 2,342
Clief Notes
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)
Powered by