I just watched the Jake Van Cleef breakdown, and the biggest thing that stood out to me was the idea of a floor plan for the project. It clicked because the IA will always understand what I’m talking about, without having to load a whole lot of context. I also find that the probability of getting wrong answers can be mitigated to near-zero, achieving a high repeatability of a process, that is something I struggled a lot with AI. What I find interesting too was the lower consumption of tokens, due to a context that only loads what it needs.

I'm currently using AI to solve small problems I find, for example I built a web app for my wife to study for her speciality as a game that makes questions based on the questions of old exams she can get from past years. Right now I'm at the exploration stage mostly but also starting to build structured systems. From the first time I saw a Jake's video on YT, the folders methodology resonated a lot with me, because it made me realize the AI has a structure and that can be ordered and interpreted as a code program for repetitive tasks and automations, but with the code being normal language.

Hey Clief Notes fam! 👋 I'm Isaías Sancho and I'm liking a lot this community. 🙋 A little about me: I'm an automation engineer, transitioning to project management. I'm from Costa Rica and I'm passionate on new technology and IA. 🎯 My current goal: My goal is to learn and adopt AI to make my work better and more valuable. 💪 What I'm currently building/working on: At the moment I'm been working on small personal projects, to help my wife with her studies or to automate some tasks on my job. I just moved to a new role so I'm always looking where AI can make the work better while going through the training. 🤔 My biggest struggle or question right now: At the moment I've been just playing with the ICM and trying and personalize it for me, but I really lack some more abilities when I encounter the moment to jump from text responses and a simple html panel to a real mobile app, for example, usable and secure. 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.