Hey, I'm 72 hours into the school community. I've been learning so much. The course has been amazing. I've already met some awesome people in here. I just want to give a general thank-you and some positive feedback saying: - Great product - Great community - Love what's going on - Learning a lot - So much value here - Appreciate everyone involved Keep cranking!

Step-by-step interactive guide from idea to output. Design an ICM workflow alongside Maya, one decision at a time, and watch a messy process become something an AI can run again and again. Right now, Maya has to try to remember what needs to be done and where each piece of information is kept. She needs a better solution. https://claude.ai/public/artifacts/7c9618f4-8324-4048-902c-cbcf77c9c102 Let’s build one with her. 😀

A quick follow-up from Weekly Comp #11: The Cartographer — I’ve been using the idea across my projects, and it has become more valuable as the systems grow. It gives Codex a clear map of the modules, dependencies, flows, and possible blast radius before making changes. In practice, it saves me time and tokens because the agent doesn’t need to repeatedly inspect the whole codebase just to understand how things connect. Even when I use ASTRA for deeper planning and audits, having the system map already available makes the process more focused and efficient. Definitely one of the competition ideas that proved genuinely useful in real project work. Thank you @Jake Van Clief and team

learning this icm framework was easy and im creating worflows and semi automations now very easily (done some personal and one for my brother), so creating part is where im good due to my experience in product management (non tech guy) but the other part is selling and giving service of creating workflows to real businesses is where im strugling. Im not sure how to find clients so may be someone here can give me a direction. One of my developer friend told me no one will buy folders. they will buy an actuall software. i showed him what i built, he was impresed but still not convinced that real businesses will use this. Learning and creating is easy now but selling is still difficult.

I've got a technical issue that needs some outside help. My background is not tech so it's not something I'm confident giving Claude an answer to so I got it to ask the question and said I'd give it any responses I got. Here's what it asked... I help run a small street food business, and we've built our internal tools as an ICM workspace. It's been working well. I've hit a structural question I'd like your view on before we change anything. The setup One folder holds four tools side by side, each a full pipeline with its own CLAUDE.md: - PRODUCTION-RUN: weekly orders in; production sheet and courier/invoice files out - SALES-HISTORY: who's buying more or less, week to week - COST-CALCULATOR: labour and ingredient cost per product - STAFF-HOURS: hours, holiday, and the monthly payroll file to the accountant The top-level CLAUDE.md only routes to the right tool. There's no shared reference folder at the top level. Our rule versus the skill Our top-level CLAUDE.md says each tool "holds its own data, and points at nothing outside itself", and that "a pointer across folders is how a suite turns into a tangle." The icm-architect skill's Umbrella form is looser. Sub-pipelines "don't share state" except through the root reference layers, and shared reference material should be linked up rather than duplicated. What actually happens Two of our tools break our own rule on purpose: - SALES-HISTORY reads PRODUCTION-RUN's weekly production sheets and its customer list. It also keeps its own snapshot of customer prices, and its own copies of older hand-kept sheets. - COST-CALCULATOR reads the same weekly production sheets. In both, only the first stage reaches across, and only once. Every later stage is told not to load anything from PRODUCTION-RUN. STAFF-HOURS reads nothing outside itself. It only mentions PRODUCTION-RUN in its notes, as a comparison. Each tool runs a check at the start of every session that reports any file path it can't find inside its own folder. So every reference to another tool gets reported as broken, every session.