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?

Built a guided way to turn work you know by heart into something you and your AI can actually use. generates a HUGE packet for you. Workflow Audit Package - The Vault · Clief Notes This is inspired by something I do in my Corporate workshops and also wanting to build something sustainable to help out the Premium and VIP members. Start with a copy-and-paste interview prompt: your AI asks one question at a time about what comes in, what you do, where things get messy, what goes out, and the decisions you want to keep. It works for business owners, consultants, subject matter experts, creators, or anyone with a recurring task they want to understand and improve. You can answer in rough words or by voice; no technical background is needed. Once you have checked the interview, give it to the included builder skill with the blank HTML template. Your AI audits the answers and creates a detailed, editable workflow package with a map of your work, evidence for where improvement could matter, open questions, practical prompts, and a recommended folder structure based on ICM: ordinary folders and readable files that give the AI the right context at each step. Open the package in your browser, correct anything it got wrong, download your copy, and use the first-test plan on a completed example you can check. Everything you need to start is in the kit; the start guide explains both copy-and-paste and file-upload options. Workflow Audit Package - The Vault · Clief Notes

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.