Yo, I’m Aaron, I’m currently using AI for planning, writing, coding and automating repetitive work. I’m at the building structured systems stage, working on making those systems more consistent and easier to manage. One idea I’m interested in exploring through the interpretable context methodology is making the context behind a task clear and reusable. That matters to me because I want to spend less time re-explaining things and correcting assumptions, and more time getting useful work finished. I’m excited to learn how to give AI the right context and clear boundaries so it can handle more of the work without overcomplicating it. My goal is simple: ship practical solutions faster, reduce back-and-forth and free up more time.

Time for a quick intro! Hey Clief Notes fam! 👋 I’m Aaron, and I’m stoked to be here. 🙋 **A little about me:** I work in marketing, operations and automation. I enjoy figuring out how to make things simpler and more efficient. 🎯 **My current goal:** Get more done with less back-and-forth, build reliable systems, and free up more time for my family. 💪 **What I’m currently building/working on:** Putting AI to practical use in my day-to-day workflow. My focus is getting simple, useful solutions finished without turning every task into a massive project. 🤔 **My biggest struggle or question right now:** Knowing when to stop planning and ship. How are you getting consistent results from AI without spending all your time managing it or adding features you don’t actually need? Let’s get it! 🚀

📣 Update (10/22/26): Comp 15 Rules Added Current Challenge: Competition 15 The Challenge 💪 - Rebuild a past comp entry. Yours or someone else's. Then prove that its better. Rules & submissions 🗒️ -https://www.skool.com/cliefnotes/weekly-comp-15-the-rebuild Good luck everyone! --- 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. --- 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 The Challenge 💪 - Build an artifact of a financial advisor client intake system Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-2-the-artifact-sprint?p=15145a68 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-2-winner-virgilio-robinson

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!