I'm going back to the fundamentals of ICM and using the AI guide to enhance my knowledge & practice. In a recent post, I commented to a community member that my school district has a new chatbot that is hallucinating athletic/school events when prompted. This highlights the importance of the routing system and how the AI should never get lost. I've used the directory method in my projects and found success but I want to ask the community: If you were giving advice to a beginner, what key features have work best for you that you would suggest baking into each project moving forward? As someone whose background is in teaching, not coding, the next area of my work that I want to clear up is around memory and second brains. I archive project notes in obsidian to have a central way for my system to learn from past projects (in separate folders) so I can improve my own processes and the system can grow as the field grows. What strategies do others use to maintain memory between projects and improve their own processes?

Just wanted to share a personal win. Thanks to this community! I've been in this community for a while. I am a current teacher and I've been building automations and systems for my school for the last year. This summer, I started doing AI consulting and website design. I landed my first paid client with a monthly retainer and built him a website using principles learned in this community. We are now exploring upsell ideas that will improve his business processes and offload his daily work so he can focus on delivering his service to his clients. I'm excited to continue to learn and grow in this community and see how structured approaches to AI can help me continue to develop great systems for myself and my clients, productize my own workflows, and grow my business. I've seen people in here over the months say they just went for it and that starting was the most important step. I decided to take the leap and I'm excited for what lies ahead!

📣 Update (8/15/26): Comp 11 Rules Added --- What this thread is: I’ve seen a number of people either not know competitions are going on or know how to find them so here is a quick single source thread where you can get to them all. I’ll keep this updated as new challenges are released. See the current challenge as well as all past challenges below! Format for community challenges: https://www.skool.com/cliefnotes/how-competitions-work-from-now-on?p=84912d60 Weekly leaderboard competition: Alongside the biweekly challenges, there is a weekly leaderboard challenge where the member at the top of the 7 day rolling leaderboard wins a free upgrade to their membership. This winner is announced on Mondays typically. @Joshua Hubbard has gone another step further and created a thread linking to all competition entries. Link here: https://www.skool.com/cliefnotes/the-competition-archive-every-entry-every-week-every-link?p=bd752987 --- Current Challenge: Competition 11 The Challenge 💪 - Build a workflow that walks a system and leaves behind a map for those that follow. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-11-the-cartographer?p=48566e59 Good luck everyone! --- Past Challenges Competition 1 The Challenge 💪 - Build a brand voice document for a pet grooming business Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/first-ever-weekly-competition-is-live?p=90f50bf9 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-1-winner-ian-barriopedro?p=0501b57e Competition 2

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!