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!

We're dropping the weekly onboarding call. Not because onboarding stopped mattering. Because a weekly 30-minute loop started mattering less than we pretended it did. If you just joined, you don't need another recurring meeting on the calendar. You need one clean pass through the room: who we are, where Discord lives, how people actually lean on each other here, and how the competitions work. Then you need to go do the work. So, the call is moving to once a month (First Wednesday of the Month). Same length. Same point. No extra theater. Next one is: Wednesday, October 7th, 2:00–2:30pm EDT https://www.skool.com/live/xTMdy25NCh8 Show up. Introduce yourself. Meet the mods. Meet the other people who just walked in. Then we walk through: - - Getting into Discord - - Finding your way around - - Getting the most out of other members - - How to win the competitions - - Quick questions at the end Thirty minutes. Straight to the point. After that, we'll run it monthly. If you miss one, the next one is a month away, not seven days. That is the point. Onboarding should be a door, not a habit. And as always, thank you for being part of the Clief Notes Community! We appreciate every single one of you.

I don't want a progress percentage today. I want to know what's actually changing. If you've been working through Building Your Stack, what is one decision you've made because of it? - Maybe you added something. - Maybe you removed something. - Maybe you realized part of your current stack makes absolutely no sense. 😂 Whatever it is, post it below. What did Building Your Stack make you rethink? And if you've been flying through the lessons but skipping the quizzes or accountability posts... Go back. Those are there to make sure you can actually explain and apply what you're learning rather than just consuming it. Drop your biggest realization below. 👇 And keep going. New roadmap next Friday, September 25th.

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.

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.