I'm currently using AI for ideation, brainstorming and developing. Right now, I'm at the building structured systems stage. One thing that caught my attention from this lesson is that life can be simple 😅. I was too much into setting up multiple agents, configuring them, and organizing them. It was a good experience, but a bit too hectic and costly as well. I'm excited to learn the ICM methodology, by just using Folders and md files, and see how default structured approaches by different LLMs can help me save costs, work together, and reduce complexity.

Hey Clief Notes fam! 👋 I'm Sarmad and I'm stoked to be here. 🙋 A little about me: A self-taught software engineer with major interest in web-apps. 🎯 My current goal: Exploring different AI Development Methodologies. 💪 What I'm currently building/working on: Exploring pathway for an upcoming complex project that requires development + technical content design 🤔 My biggest struggle or question right now: Finalizing a one-for-all schema to handle multiple projects of different nature, using different models for different kind of works, while staying updated with community-contributions on the internet. Let's get it! 🚀

I heard someone say "what Tony Stark's Jarvis is really about." It's been rattling around my head ever since, so I sat down and wrote out why. Short version: Jarvis was never an app. He wasn't even "an AI" the way we toss the word around. He was a brain that used tools — and that distinction is the whole game. The models and agents are tools. A pile of tools isn't intelligence. The intelligence is the operating system you build on top: how you structure your thinking, your context, your folders, so the system grows instead of resetting every morning. A lot of you here already know this in your bones — it's the ICM way of working, and this community runs on it. I just took it somewhere specific and wrote up what I found: Commodore 64s, why you can't sell a folder, and the questions worth asking before you save one more prompt to the pile. Full piece 👇 https://medium.com/@gabeyoga/you-dont-have-an-ai-problem-you-have-an-operating-system-problem-f281afd4fadd And the real question I'd love answered, not a rhetorical one: if were building your own operating system, what's the first folder you'd open, the first path you'd lay down?

I've been tinkering with a question. Some of the applications I'm building might use specialized agents deployed online. Think off a customer service agent. My whole process is built with ICM and that agent or agents have their whole structure, it works locally, they have their context, reference files, rules, all the good stuff. However, they live in my folders in my PC. And I know how to deployed apps online, I mean there's a whole bunch of examples here on how to do it. But how do I do that for agents? I know it is a play of the Claude API embedded into the website or whichever place I need it into. But how do I direct that API to work though my whole ICM architecture for that specific agent so it knows the right context? Example: Customer asks about product A, the agent knows through the context.md that all product A info is in Product A's folder so it needs to go there and read the relevant files. All that is great and works locally but how do I deploy it online?

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