4d (edited) • 📢 Announcements
Community Guidelines
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.
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.
6. Respect every level.
Someone who joined yesterday is as welcome as someone who's been here since day one. Asking a beginner question in front of a crowd takes more nerve than answering one, so "just ask Claude" and "google it" are not replies. If a question is beneath you, scroll past it.
And the one that shouldn't need saying: no harassment, no insults, no discrimination, no aggression. This community argues about tooling constantly and that's healthy, but argue with the idea and not the person.
7. Keep it on topic.
ICM, context engineering, agents, the tooling, and the real builds and businesses you run with them. Model releases, hardware, cost breakdowns and workflow arguments all count. Generic AI hype, crypto, and unrelated ventures don't.
8. Protect the community.
Comment spam arrives in waves, and accounts will DM you pretending to be Jake or a moderator. No admin here will ever DM you first about a payment, an investment, or a special offer. Report it and don't engage. If something looks like a scam, say so publicly with the receipt attached (a link, a screenshot) so people can judge it for themselves.
9. Search before you post.
A lot of questions in here have already been answered well, sometimes several times over. Search first. And if you find your answer in an old thread, drop the link in a new comment where people are asking again. That's the only thing that stops a good answer from staying buried.
10. Post the failures too.
"This didn't work and here's exactly where it broke" saves more people more time than another success story. The most valuable posts in this community are the ones that show the version that fell over before the version that worked.
11. Write your own posts.
Use models for everything, obviously. But if a post reads like it was generated, that's how people will read it. Your typos are more convincing than perfect structure. One real number out of your own work (what it cost, what broke, how long it took) beats a clean framework nobody can verify.
12. Close your loops.
If people show up in your thread with follow up questions, answer them. This matters more than it looks, because the next person searching that topic finds your thread, finds the unanswered question, and leaves with nothing. Threads here are documentation whether you meant them to be or not.
What gets removed:
- Almost everything here is a conversation first. These are the exceptions:
- Harassment, insults, discrimination, or aggressive behaviour toward another member.
- Advertising. Crypto offers, lead-gen, agency pitches, anything posted to sell rather than to help.
- Piracy. Cracked software, paid courses reposted, copyrighted material. Respect the people who make the things we build with.
- Comment spam. One to four word replies posted at volume to farm visibility. Length is not the issue, value is: if every comment carries something real, post as much as you like.
- Low effort posts, per rule 3.
- Scam and spam accounts, removed on sight without warning.
How this is enforced:
- Moderators can remove posts, and members, to keep the room working. Outside the list above that's a last resort: almost every problem here is someone new not knowing the room yet, so it starts as a comment or a DM from a moderator.
- As a member of the community, you have a right to appeal a warn, deletion of a comment/post or a ban.
This document gets updated. If something is missing or worded badly, say so in the comments and it gets folded in rather than argued about.
Last updated: 29/07/2026
101
24 comments
Community Guidelines
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+1393
2
+1298
3
+1227
4
+634
5
+606
Powered by