Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
What is this?
Less
More

Memberships

Clief Notes

43k members • Free

9 contributions to Clief Notes
🛠️ New tool: ICM Architect
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. 👇
3 likes • 8d
So, how to keep the context files updated routinely? As a codebase gets bigger and bigger, the context files begin to get outdated which seems like it could create token bloat as the model tries to resolve the discrepancy between what is in the docs and what is in the code. For example, if I'm serving images from an API but the host has a limit on the time of requests that conflicts with the request timeout, and the UI breaks a little, and on and on, then how to make sure everything stays lean and efficient? Like a hook that autoscans for code changes in the gitrepo and then that feeds back to a skill? A metaskill? (dyamically coded skill? ) sorry if that was a lot 🤣
1 like • 7d
@Billa Coetsee so what is the part of this that keeps it preserved? At the end of the session do you call the skill to update the docs in the architecture? Or dynamically as changes are made? Also, out of curiosity, what is GitLab compared to GitHub?
🏁 Foundations 2.6 Check-In
You just saw how video production turns into code. Vote below, then tell us in the comments: what is one repetitive creative task in your work that could become a pipeline?
Poll
675 members have voted
1 like • May 24
@Austin Richardson The most important thing here is learning the way of thinking. It's about improving the problem solving by complimenting it with a solid process. Once breaking it down into the individual components becomes more of second nature, many more things become possible
0 likes • May 24
How to make it not take up 60k tokens to make 30 seconds of video?
🏁 Playbooks 1.1 Check-In
The full animation workflow: Script → Spec → Build → Render. Where'd you land after watching?
Poll
156 members have voted
1 like • May 24
I made it through. It used an incredible amount of tokens to create something that looked much worse than something I could create with capcut. Maybe there's something I am not doing correctly, but that was very underwhelming. How to make it use less tokens? Use haiku?
1 like • May 24
@Logan Harris I'm well, and how about you?
🏁 Foundations 2.5 Check-In
This one breaks down orchestration. Vote below, then pick one AI tool you actually use and tell us in the comments: can you identify which part is the model and which part is the routing layer around it?
Poll
728 members have voted
0 likes • May 18
The tools that I'm using are Codex, antigravity, and claude code. Besides that, skills within these interfaces. I have heard that antigravity is basically a wrapper for VS code, and so in that sense the UI in all these cases is just a pretty wrapper for the CLI. The tools are basically also just fancy prompts and instructions that tell the model what to do.
0 likes • May 18
@Jeff Van Leenen I've tried to do this to systematically pull from a lot of documents, and it seems to have issues. I'm thinking maybe putting the component documents in a folder in the tree structure will help? We will see
🏁 Foundations 2.3 Check-In
This one reframes what prompting actually is. Vote below, then fill in the blank in the comments: Before this, I thought prompting was ___. Now I think it is ___.
Poll
786 members have voted
1 like • May 18
Before, I didn't have much of a concept of what prompting was. Now I have much more of an understanding. I started out giving it very clear prompting, then as I got better at prompting and the models got better, I slacked off a bit. Now I'm coming back to a more systematic understanding of how to give it very clear instructions to get results. This "folder" understanding is great, and I want to know how to expand the thinking to Claude and Antigravity as well. Is it the same?
1-9 of 9
David Graham
3
45 points to level up
@david-graham-6115
Kindergarten teacher who is starting a small software company.

Active 5d ago
Joined May 12, 2026
Powered by