Subject: Am I misunderstanding "build inside your workspace"? I'm working through "Building Your Stack" and stuck on something Jake says in lesson 1.1: "Build inside your workspace. Don't create a separate folder. Build where your context already lives." Right now, every time I start a new project, I create a new folder and ask Claude to use the ICM architecture to design it. But based on this lesson, it sounds like I might be doing something wrong. My current approach: - New project = new folder - Each folder gets its own CLAUDE.md and structure - I reference ICM architecture in the setup What I think Jake is saying (but not sure): - Build tools and projects inside an existing workspace that already has context - Don't spin up a new isolated folder every time Questions: 1. Is there a "main workspace" I should be building everything inside of? 2. Should custom tools live alongside my regular AI work files, not in separate repos? 3. Am I overthinking this, or am I actually setting things up wrong? Would appreciate any clarity from people who've gotten this working.

Hey Clief Notes fam! 👋 I'm Edgar and I'm stoked to be here. 🙋 A little about me: I'm a paediatric intensive care consultant in Glasgow. Alongside that I run a small family travel business and do Maltese consular work. 🎯 My current goal: I've used ChatGPT for over three years and got comfortable with it — but that's level one, level two. I want level three: answers that are actually personal to me, not generic. 💪 What I'm currently building/working on: Working through this keeps bombarding me with ideas — for the hospital, for work, for everyday tasks — way bigger than what I came here for. The core of it is building my second brain, to automate things I do regularly, like post creation for the travel business and other areas. I've started venturing into Hermes, set up on an old computer, and Cogni on another, connecting them through Tailscale. Structurally I started trying to build one big folder for everything; I've since moved away from that to a separate folder for each element, with a plan to integrate them later — it keeps me more focused when I'm working on one piece at a time. 🤔 My biggest struggle or question right now: Time. I wish I had more of it to really invest in this. How do I split my time between learning this properly and actually living my free time, rather than spending it sitting down reading? Let's get it! 🚀 Would love to get to know as many of you.

📣 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.

The intro of this video isn't original, It's inspired by Luda's "Got any hobbies?" — right down to the title being "got many jobs?". His film is the reason I started paying attention to how an intro is actually built: the macro shots on the table, the doodles scribbled over the footage, holding on a face about two seconds longer than feels comfortable. His is on the left. Mine is on the right. What I got out of copying it beat for beat was the thing I actually needed. You learn more rebuilding one film you love than you do watching fifty you like. If you want the rest, the trimmed class is 22 minutes: the six levels of AI filmmaking, and the collage sequences I built to explain them. https://youtu.be/7edameF6MDI So, what video are you making ?