Hi, I'm Gary here, and I'm here to share my AI journey! I'm currently using AI for all kinds of things, but a regular thing I do is generate html slides for presentations. I work as a university tutor and like to put together presentations for my students to help them understand the content we are working on during a given week. AI has been a big help with deciding what to include or not include, what things warrant a deeper explanation or even a demonstration. I'm fairly comfortable with building structured systems, but am very new when it comes to using AI and discovered this community because I want to do things the right way and what Jake is teaching makes sense. It still feels like the wild west out there, but Jakes method just feels solid. A good framework that will serve you six months from now, and six years from now! One thing that caught my attention from this lesson is it's overall simplicity. Files and folders being navigated by a single agent strips away the complexity and shows that this isn't voodoo! I'm excited to learn how to apply this methodology to all of my projects and see how structured approaches to AI can help me not only build better systems, but to do it in a way that stays resilient well into the future!

Hey Clief Notes fam! 👋 I'm Gary and I'm stoked to be here. 🙋 A little about me: I'm a tech enthusiast who works in education. 🎯 My current goal: I'm in the process of educating myself (a lifelong pursuit) in the world of AI and making it accessible to non-technical people. 💪 What I'm currently building/working on: Currently I am putting together a guide to help people get set up and building stuff with AI on a budget, using local and free-tier models. 🤔 My biggest struggle or question right now: Since I am learning myself, I am most concerned about learning the best approach and managing expectations of what the model being used are currently capable of. Let's get it! 🚀

📣 Update (8/3/26): Comp 10 Rules Added, Submissions Due by 8/8 11:59 PM, Winner Announced 8/15 --- 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 10 The Challenge 💪 - Build a full folder-based diagnostic auditor that tells you why something is broken. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-10-the-diagnostician?p=367505f3 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

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!