📣 Update (9/7/26): Comp 12 Rules Added --- What this thread is: I’ve seen a number of people either not know competitions are going on or know how to find them so here is a quick single source thread where you can get to them all. I’ll keep this updated as new challenges are released. See the current challenge as well as all past challenges below! Format for community challenges: https://www.skool.com/cliefnotes/how-competitions-work-from-now-on?p=84912d60 Weekly leaderboard competition: Alongside the biweekly challenges, there is a weekly leaderboard challenge where the member at the top of the 7 day rolling leaderboard wins a free upgrade to their membership. This winner is announced on Mondays typically. @Joshua Hubbard has gone another step further and created a thread linking to all competition entries. Link here: https://www.skool.com/cliefnotes/the-competition-archive-every-entry-every-week-every-link?p=bd752987 --- Current Challenge: Competition 12 The Challenge 💪 - Build an auditor that reviews something against a defined standard. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-11-the-auditor?p=1d0eb170 Good luck everyone! --- Past Challenges Competition 1 The Challenge 💪 - Build a brand voice document for a pet grooming business Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/first-ever-weekly-competition-is-live?p=90f50bf9 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-1-winner-ian-barriopedro?p=0501b57e Competition 2 The Challenge 💪 - Build an artifact of a financial advisor client intake system

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.

I have found myself wasting my time arguing with Claude regarding working or versions of standard operating procedures across my existing architecture. Every time I get moving forward with mapping out and building - all my older files pointers or wording is stale. Should my initial "Layer 0" curation begin from scratch - and once it can finally pass a 'walk test' - allow for Claude to edit / update it? I'll have a few days of needing to just work on real world timeline constraints - then return to trying to build out an Icm-architect inspired folder / file system - and Claude is nonstop updating or conflicting with small details that I do not believe that I am asking for it to create in the first place. Should I take this opportunity to just start fresh and follow Icm-architect explicitly? I feel like being able to enter into a pre-existing organization system is realistic - so wiping everything clean and starting from scratch seems ideal, but not appropriate for interaction with existing organization models

Had our team's quarterly planning this past Friday and I'm super excited that they're gonna join Clief Notes to go through The Foundations course! Jake is such a rare find and there's no words that can express the gratitude. But we sometimes forget that gratitude can be expressed via actions, and I'm telling anyone who's willing to hear about Clief Notes. Even got my son in there LOL! Out of all my kids, he's the one with the most interest and his brain is best wired to dive into a community like this.