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.

A few days in. Starting to see where the Clief Notes AI is actually becoming useful. Some of you are using it to figure out where to start. Others are asking specific questions and getting pointed back to lessons or drops they didn’t even know existed. And some are basically using it as search: “Have we covered this before?” That last one alone saves a lot of scrolling. @Anthony Brady shared a really good example of how he’s been using it. He said the agent has been helping him find the right lessons, figure out where to go next, and actually apply the material to what he’s building. He’s even been pushing it with harder questions, and when it doesn’t know something, it tells him instead of just making something up. What I really liked was how he described using the tools together: The agent helps him navigate. NotebookLM helps him go deeper. And Decster keeps him moving through the course, completing assignments, and staying active in the community. That’s exactly what we want this to become. Not another AI tool you open once and forget about. Something that actually helps you use everything already inside Clief Notes and keep moving forward. We’ve also caught a few questions where the agent could’ve pointed somewhere better. Keep sending those. The more you use it, the better we can make the experience. This thing should get more useful as we see how you actually use it. If you haven’t tried it yet, start simple. Ask it the next question you would normally post in the community. Have you tried it already? If not, comment “Navigator” and I’ll send you access to it.