1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

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. 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 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. 5. No spam, no pitching. Sharing a tool you actually use and explaining why you use it is fine. Dropping a link with no context, cold DMing members, or treating the feed as a lead list is not. Networking is genuinely welcome (there's a Connection Hub for exactly that: https://www.skool.com/cliefnotes/new-the-connection-hub-is-live) but networking and pitching are not the same thing, and everyone can tell the difference immediately.

Gather round, Clief Notes crew — we’re opening The Legends: a classroom on the Frontier built around two gunslingers who deliver real systems, not hype. Each legend has a dedicated folder packed with signature builds, frameworks, and battle-tested wisdom. Start where the dust is thickest for you. 📐 Bas Rosario – The Wise Architect’s Library Master planner and blueprint boss. Bas designs for deep understanding and human–AI collaboration so you stay in control — frameworks, systems thinking, responsible AI, and work that still feels human. 👷‍♂️ Don Roy – The Master Builder’s Forge Hammer in hand, fire in the forge. Don turns ideas into working tools: automation, quality control, content systems, Remotion + AI builds, and anti-slop standards that keep what you ship durable. These two are the heartbeat of this classroom — grinding, growing, and lifting the whole crew. Your move: Pick a folder. Open it. Start forging. https://www.skool.com/cliefnotes/classroom/b5143824?md=61c684c877384eefbd11c804f83aac05 Who are you riding with first — Architect or Builder? Drop a 🤠 below and go make something that lasts.