It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

How are you guys using ICM folders to do development? ICM architecture works great with repeated tasks but programming a project requires a long list of different features (backend, frontend, art assets, etc). My main ICM uses now are a /feature-intake that writes implementation specs to a roadmap.md, /needs-review, and a decision-log.md (the index for a bigger historical decision-log-detailed.md). What I'd ideally want longterm is an ICM folder working as a development studio; I give a high level request in a document (e.g., I want to create a mobile app that [does xyz]", then it reviews->brainstorms, finds courses of action->specs it out->develops->reviews->final corrections. Just curious how everyone else is building projects with ICM.

Has anyone in the community utilized this structure? Any words of wisdom? I'm jumping in head first into a game based learning app and was insanely overwhelmed at the thought of figuring out how to structure everything considering I have zero game engineering experience. I used the Prompt structure to educate myself on the vocabulary etc etc and this was one of the resources listed in the Output from Claude. https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main It's late, I'm tired and signing off in a moment, but my thoughts about where to start tomorrow are to set up a Pre-Development Project for the purpose of getting prepared to customize the structure above for my project. In "Project Pre-Dev" my goal will be to fairly efficiently provide Claude with the context needed to help me with the customization of the entire structure. Is that crazy or am I on the right track? On one hand it seems redundant, but on the other hand, I think that I could essentially break the setup down into distinct projects and save myself a lot of slogging around trying to decide what to do in chat sessions.

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

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.