It's the end of the week and I had tokens to burn. So I left Claude running a self-improvement loop this afternoon and went out to color. Oh yeah, I've got into coloring lately. Most people working with AI are babysitting it. One prompt, wait, watch, next prompt. Stuck in the loop. Every output needs you, right now, watching. But the work isn't the prompting. The work is the workflow. ————————————————————————————————— Build it once and the shape changes: - In the loop: you design the process, set the gates, define what good looks like. - On the loop: it runs in the background. You check at the gates and redirect when needed. - Out of the loop: it runs without you. You start another Claude session, or you go and color. The loop I left running today didn't need me. I'd already done the part that needed me. That's the whole trick. Pay the attention up front, once, on the system. Then the system buys it back. You free up the time for another session, or for a life. ——————————————————————————————————— You don't scale by prompting faster. You scale by being in the loop once and building workflows. /A<3

Hey guys — honestly just looking for some real feedback from people in here because you guys always give solid insight. I’ve been building two websites over the last while and they’re finally getting close to being “done.” There’s still a few small tweaks and refinements I want to make, but overall the core vision is there now. One is my personal practice/project:jaydenforshee.com It’s built around ICM with an ontological layer on top of it and is more of a personal/creative/philosophical expression. The second is my AI agency + infrastructure work:griffain.app Would seriously appreciate if you guys could check them out and give feedback on: - UI/UX - Flow/navigation - Functionality - Copy/writing - Mobile responsiveness - Overall feel/impression Desktop/laptop is probably the best experience right now lol, but mobile should work pretty well too. I’m mainly trying to catch blind spots before I fully call them finished. Appreciate anyone who takes the time to look through them 🙏.

Global in the host like VS Code = not portable ICM = portable ICM workspaces' entire premise is that you don't need specialized tooling, protocols, or frameworks to orchestrate a multi-step AI workflow. The "protocol" in ICM is the filesystem itself, meaning numbered folders, markdown files, plain text handoffs. Etc.. In the 60% 30% 10% Having a local script (at the 60%) that runs, writes the results in a stage's output folder as an .md file and so on.. is fine. In the spirit of ICM's portability, should MCP live in the skills folder? If not, where? What is the community's way to address data that's outside the workspace whether input or output? Thank you all in advance.

💰 $500 CASH 💰 Win this and you've covered a year of Premium with $175 left over. 📋 THE CHALLENGE Build a folder-based AI coach for a specific domain. You pick the domain. This week's deliverable is one coach folder that someone could drop into a Claude project and use as their personal coach for whatever you've built it for. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎤 Public speaking coach for new managers giving their first big presentations - 💼 Salary negotiation coach for tech workers at Series A startups - 📞 Cold call coach for first-year SDRs in B2B software - 🎯 Interview prep coach for product manager roles - ✍️ Writing coach for one specific genre (sci-fi short stories, college essays, op-eds) - 🏋️ Fitness form coach for one movement (squat, deadlift, golf swing) - 🌍 Language learning coach for one use case (medical Spanish, business Mandarin) - ♟️ Chess coach for one specific opening or endgame pattern - ⚽ Youth athletics coach for one sport and age group The more specific, the better. "Life coach" is too broad. "Salary negotiation coach for tech workers at Series A startups" is right. 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning the foundation of interpretable context methodology. Folders as architecture. Each file does one job well. Your coach is a folder with five things: - 📄 identity.md (who the coach is) - 📐 rules.md (how they coach) - 💬 examples.md (what good looks like) - 📚 reference/ (frameworks, drills, source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the coach. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK A coach is NOT a knowledge base. A coach gives feedback. Pushes back. Asks better questions. Holds people accountable.

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.