I explain the details about it on today's high tea . I built a Claude skill that turns a process, an idea, or a messy folder into an ICM workspace. The folder structure does the orchestration. Numbered folders carry the order, the hierarchy scopes context, and plain markdown files hold state. One agent walks the right files at the right time and does the work a multi-agent setup would. Repo: github.com/RinDig/icm-architect 📦 What it does Two modes. 🔨 Build. You describe your work and it pulls out the structure already sitting in how you talk about it. The stages, the points where you stop and check, what stays the same every run versus what is new. Then it picks one of five proven forms and scaffolds the smallest workspace that carries the job. ♻️ Restructure. Point it at a folder, repo, or vault you already have. It reads every file, sorts each one by role, shows you a migration map, waits for your yes, then moves and checks the result. 🧩 The five forms Pipeline, umbrella, record library, knowledge bundle, context map. They mix and nest, so most real workspaces use more than one. ✅ The walk test Every result gets checked cold. An agent with no memory has to open the root, find its way, act, and report status from the files alone. If it can't, the structure gets fixed until it can. ⚙️ How to use it You can honestly just tell claude to download it from the link, but if you're using codex or something else it will just have to restructure the claude.md to agents.md Or if you want to do more Hands-On install Claude Code: drop the folder in ~/.claude/skills/icm-architect/, then say "ICM this" or "build me a workspace for X." Claude apps: zip the folder and upload it under Settings, then Capabilities. Fork it, break it, tell me what you built. 👇

You built your first folder. Vote below, then drop a screenshot in the comments so we can see what you came up with.

Sat down with Katie Bakewell, a data scientist who's been building this since 2011, back when it was still just called "natural language processing" 🧮 She came up through math (DNA computing, time series on commodities) and thinks about problems like proofs, not recipes. What we get into: 🪨 The Indiana Jones "build me a chatbot" boulder she ran from in 2023 🚨 The 7 neural nets that "found" a signal that was completely fake 🏎️ A $5M Pagani vs a $100 Toyota, and why "best" is a trap 🤖 The first chatbot was built in 1966 (ELIZA)... these aren't new ideas 🐬 Meta's SAM3 turning hours of labeling dolphin fins into a single prompt 🧠 Why half the companies asking for AI are solving the wrong problem ▶️ Go watch 💬 Then drop a comment: What surprised you most, or what would you have asked her? Happy learning 🙌

Hey everyone, I'm new here and really want to learn how to use AI in my business. I've watched Jake videos on folders and the setup, but honestly, I'm overwhelmed. There's so much information and I'm not connecting the dots yet. I learn best when things are broken down into simple steps. Could someone point me to: - The absolute basics to start with (like "do this first, then this") - A simple first project I can complete to understand how it works - Which parts I can ignore for now as a beginner I'm committed to learning this, but I need a clearer starting point. Any guidance would be really appreciated. Thanks for understanding!

Someone shared that a person a reaction video was made about my method and at first I was nervous but immediately it was amazing praise. I have never met with this person one-on-one and I haven't paid them or done anything other than post my own videos ! I think they do a great job at breaking some of the concepts down. It does an amazing job of breaking down some of the logic especially some parts where I go ranting in my video he slows it down a bunch ! Much needed