Hi everyone 👋 I just joined and I'm excited to be here. I'm looking to build a solid foundation in AI rather than just chase the latest tools. Looking forward to learning from everyone, applying what I learn, and contributing along the way. Happy to be part of the community

Clear your context when completing a task. It sounds simple but this is something I think everyone learns too late on their journey to becoming AI literate. When you keep messaging your model in the same session, your usage piles up, the model performs worse, and you are left with less output because of both of those outcomes. The fix is simple, whenever I am done with a task, and the next one doesn’t need all the information in the chat, I clear the session. Even if half of the inputs overlap, it’s not worth wasting the other half. Keep an eye out for the next one! Want to see the rest ahead of the videos? Head to the classroom 👇 https://www.skool.com/cliefnotes/classroom/b5143824?md=367fe0cb353f44f28e1eb493dbe40054

Feed these papers to your ai and ask it if it thinks they work well WITH the ICM. They aren't here to replace anything. They are the gang ICM didn't know it started. OGM: https://doi.org/10.6084/m9.figshare.33106949 EEM: https://doi.org/10.6084/m9.figshare.33106970 OACM: https://doi.org/10.6084/m9.figshare.33106985

I'm running a startup incubator in Suriname and for a young "AI for geology & mining" startup I'm trying to get ICM in the mix: Workflows - for the business aspects design - design, coding and maintenance of the software (front end/back-end) - The actual AI engine running the service, setup, training, optimization, uptime etc. - Monitoring users, errors, UX - Monitoring business progress/KPI's/CAP tables for Stock Splits Anybody knows how best to structure all of this? Best practices? Oh and I manage currently 4 active startups

Have been fiddling with ICM, Hermes, GSD, BMAD, taskMaster etc. They all sound perfect and logical on their own but feel "out of control" somehow so put it inside of ICM. I tried to make sense of them all and cook up an ICM here: .icm/ ├── CLAUDE.md # Upgrade safety gates, rollback hooks, and CLI routines ├── .icm.env # NEW: Central environment vars feeding variables to scripts │ ├── 00-gsd-wave-governor/ # CONTEXT & SPREAD CONTROL │ ├── contract.md # Rules: Blast-radius mitigation, branch naming, strict file locks │ └── active_wave.md # Tracks the current migration delta and target files │ ├── 01-discovery-and-party/ # LEGACY ANALYSES & DEBATE │ ├── contract.md # Rules: Analysis must document side-effects before code editing │ ├── codebase_discovery.md # Static analysis logs, dependency graphs, and tech debt maps │ ├── 00-party-room/ # BMAD Party Mode: "Refactor vs. Wrap" architectural battles │ │ ├── system_prompt.md # Personas (Winston/Arch, John/PM, Safety-QA Specialist) │ │ └── migration_consensus.md # Binding agreement on the upgrade strategy & fallback path │ └── 01-feedback-loops/ # Regression and breaking change post-mortems │ ├── 02-taskmaster-decomp/ # MIGRATION STEP DECOMPOSITION │ └── todo/ # Micro-tasks focused on localized refactoring steps │ └── 03-bmad-assembly-line/ # IMPLEMENTATION & REGRESSION TESTING │ ├── 01-architect-spec/ # BMAD Role: Designing code deltas & backward compatibility │ ├── 02-dev-workspace/ # BMAD Role: Executing precise, isolated modifications │ └── 03-qa-sandbox/ # BMAD Role: Core regression suite, smoke tests, validation