I keep running into issues with organizing my file structure. I keep having to tell my chats to review the ICM templates and examples to make sure workflows are structured accordingly, but I still feel like i'm all over the place. Has anyone else had similar issues or suggestions for assistance. It feels like it takes hours just to create one workflow, let alone test it🫠. I already have a workflow and skills for creating the files and folder organization but still having issue!

This week's roadmap is officially open: Building Your Stack. And I want you to approach this one differently. As you go through it, don't just ask yourself: "Do I understand this?" "What does this look like for me?" You'll be working through lessons, quizzes, and accountability posts designed to make you stop and actually think through what you're building. Some of the accountability steps will ask you to summarize what you've learned. Others will force you to make decisions about how you're going to apply it. By the time you reach the end, I don't want you to just know more. I want you to have something clearer than what you started with. Take your time with this one. If you get stuck, ask the Clief Notes AI questions along the way. It knows the material and can help you find the right lesson or work through something you don't fully understand. Building Your Stack is available now for Premium and VIP members. Premium and VIP also unlock: - Live calls with me - Unlimited conversations with the Clief Notes AI - All of our new roadmap quizzes and accountability challenges - Early access to the new Decster features we're building If you haven't upgraded yet, you can do that here: https://www.skool.com/cliefnotes/plans If you're already Premium or VIP... Your stack isn't going to build itself. 🧱 Head to the Roadmap tab and get started.

📣 Update (9/20/26): Comp 13 Rules Added Current Challenge: Competition 13 The Challenge 💪 - Build a folder-based AI translator that takes one kind of work and turns it into another kind of work. Same shape in, same shape out, every time. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-13-the-translator 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. @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 --- 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!