Apologies if this topic has already been covered. My thought was to have Jake’s folder structure as my main Ai Operating System and then have a wiki or second brain where I can dump thoughts, ideas, past decisions, mistakes, lessons etc. Combining Jake and Karpathys concepts into one. The second brain knowledge base would be called on when needed for tasks that I call within the folder structure. Bear with me if I’ve gotten some concepts or terms wrong - still learning lots about all of this stuff 😳🤯 Does this make sense or am I missing something important here?

📊 You've probably seen this chart floating around LinkedIn and Twitter Each dot is 3.2 million people. ⬜ Grey is the 84% of humans who have never used AI 🟩 Green is the 16% who have used a free chatbot 🟨 Yellow is the 0.3% who pay for one 🟥 Red is the tiny sliver who use AI coding tools Most of the people sharing it have not actually said what it means. So here it is. 🔁 We live inside an algorithm. Mine shows me AI all day. Yours probably does too. Every reel, every post, every podcast clip, every ad. The feed makes it feel like the whole world has moved on without you and you are sprinting to keep up. Inside Clief Notes that feeling gets louder. You log in and see people building agents, shipping side projects, automating their inbox, talking about Claude Code and MCP servers like it is normal. In this room, it is. Step outside and almost nobody is doing any of it. 6.8 billion people have never opened a chatbot. Plenty of the ones who did opened it once, asked it something dumb, got a dumb answer, and decided the whole thing sucked. They are not coming back this year. Maybe not next year either. 🪖 When I was in the Marine Corps I never felt like I was doing anything special. I was surrounded by other Marines. Everyone around me could do what I could do. The standard was the standard. It was not until I left and stood next to people who had never served that I understood. The thing I thought was ordinary was rare. I just could not see it because I was inside it. That is what is happening to you in here. If you feel behind in this community, that is the right feeling to have. It means you are standing next to the people pushing the edge. Step outside this room and the thing you are calling behind is so far ahead of where most of the world is sitting that they cannot see you from where they are. And do not forget. The thing you built last week, the workflow you set up this morning, the conversation you just had with Claude. A version of you from two years ago would have paid good money to do any of it.

Hey everyone, Looking for your best tips to optimize token usage in Claude Code. My issue: I have a fairly heavy file stack ( multiple CLAUDE.md files, context files, auto-memory, etc.). Every new conversation starts with a large amount of cached tokens loaded before I even type my first message. I hit limits fast and can't work efficiently on longer tasks anymore. Would love to know: - How do you manage your context files to avoid loading everything each time? - Any practices to slim down /context or CLAUDE.md files? - Ways to structure a project so Claude doesn't load everything unnecessarily? for exemple : Cached: 54.9k | In: 954 | Out: 10.5k | Total: 54.9k -> after 1 message Thanks in advance!

1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). 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, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?