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.

Thought I’d give everyone a proper update on where BuilderCore is. The backend has reached a point where I’m finally running real trial projects through the entire system. At the moment, the focus isn’t adding new features—it’s debugging, validating and making sure every stage behaves exactly as intended. Some of the biggest challenges so far: • The UI is constantly playing catch-up. I naturally move much faster on backend architecture than frontend, so a lot of the recent work has been making the platform usable rather than just functional. • Governance is hard. The biggest challenge isn’t getting AI to generate code—it’s making sure work can only progress when the correct gates have been passed. Planning, implementation, review, validation and operator approval all have to happen in the right order, every time. • Testing is everything. Building the platform turned out to be only half the job. The real challenge is debugging it until it behaves exactly how you imagined. Every trial uncovers edge cases that you’d never think of on paper. • Model limitations are real. One thing I’ve learned is that different models genuinely excel at different tasks. At the moment, my own experience has been: 1. Fable 5 2. GPT-5.6 3. Claude Opus 5 None of them are perfect, and usage limits are still a genuine bottleneck when you’re building complex AI systems every day. Right now BuilderCore is successfully working through trial projects, and each run helps expose another issue to fix. Once I’m happy with a single project, the next milestone is running multiple projects simultaneously and making sure the orchestration scales properly. If all goes to plan, I should have a proper demo to share soon. It’s been six months of building, breaking, rebuilding and learning, but it’s finally starting to feel like a real platform rather than just an idea. Looking forward to showing everyone what it can actually do. 🚀