I'm interested in what people think about this. I've been working with Cloudflare for many months, building free sites using their Workers/Pages feature. Anyone else doing this? I see people talking about Vercel but I don't know why I would consider using Vercel yet. Maybe I'll use them side by side. Here is a comparison:

Hey guys — honestly just looking for some real feedback from people in here because you guys always give solid insight. I’ve been building two websites over the last while and they’re finally getting close to being “done.” There’s still a few small tweaks and refinements I want to make, but overall the core vision is there now. One is my personal practice/project:jaydenforshee.com It’s built around ICM with an ontological layer on top of it and is more of a personal/creative/philosophical expression. The second is my AI agency + infrastructure work:griffain.app Would seriously appreciate if you guys could check them out and give feedback on: - UI/UX - Flow/navigation - Functionality - Copy/writing - Mobile responsiveness - Overall feel/impression Desktop/laptop is probably the best experience right now lol, but mobile should work pretty well too. I’m mainly trying to catch blind spots before I fully call them finished. Appreciate anyone who takes the time to look through them 🙏.

Hello everyone! 👋☺️ I know Jake covers some really foundational and impactful information about his ICM methodology, and I have been handing out the links to the earlier resources in the library. I wanted to be a bit more helpful in this mission, So, I made a little resource to make guiding newer people to the more impactful content on their ICM journeys. 🌐 Ask Jake's Library → https://askjakeslibrary.com/ A few things I want to be clear about: 🔒 It doesn't scrape, copy, or redistribute any content. All traffic goes straight to Jake's lessons on Skool. It just makes the early stuff easier to find. 🆓 Completely free. No catch. Bookmark it and it's there whenever you need it. ✅ It's a navigation layer, not a content layer. ❌ I'll take it down right away if it's not ok. (I want to help the community, not break any rules.) It's a free bookmark that helps you find Jake's get-started content easily. The content on the site is guided, just tap a path and it points you straight to the right lessons, and every link opens right back here in Skool. Made for folks who are new, or just learning Jake's ICM. Think of it like a librarian sitting on top of Jake's foundational lessons, pointing you to what you need as you learn. If you want to jump in on your journey 🗺️ Footnote → Margin → Highlight → Index → Compiler → Architect → Orchestrator.: This is the path that will get you there! /get started : orientation /folderstructure : see how everything's organized /whatisicm : if you're new to the methodology Why I made it: Jake's content is genuinely some of the best material I've come across for building real systems online, and he's giving it away. 😇 I just wanted to make it a little easier for people who are new, or learning ICM, to find what they need when they need it. 💪💭🌜We all have DREAMS! I want to build for people, wherever they are part of a company, part of a businesses, or if it's just for myself. I made this one because this community have given me a lot, and I wanted to give something back. 🛠️

It's the end of the week and I had tokens to burn. So I left Claude running a self-improvement loop this afternoon and went out to color. Oh yeah, I've got into coloring lately. Most people working with AI are babysitting it. One prompt, wait, watch, next prompt. Stuck in the loop. Every output needs you, right now, watching. But the work isn't the prompting. The work is the workflow. ————————————————————————————————— Build it once and the shape changes: - In the loop: you design the process, set the gates, define what good looks like. - On the loop: it runs in the background. You check at the gates and redirect when needed. - Out of the loop: it runs without you. You start another Claude session, or you go and color. The loop I left running today didn't need me. I'd already done the part that needed me. That's the whole trick. Pay the attention up front, once, on the system. Then the system buys it back. You free up the time for another session, or for a life. ——————————————————————————————————— You don't scale by prompting faster. You scale by being in the loop once and building workflows. /A<3

Global in the host like VS Code = not portable ICM = portable ICM workspaces' entire premise is that you don't need specialized tooling, protocols, or frameworks to orchestrate a multi-step AI workflow. The "protocol" in ICM is the filesystem itself, meaning numbered folders, markdown files, plain text handoffs. Etc.. In the 60% 30% 10% Having a local script (at the 60%) that runs, writes the results in a stage's output folder as an .md file and so on.. is fine. In the spirit of ICM's portability, should MCP live in the skills folder? If not, where? What is the community's way to address data that's outside the workspace whether input or output? Thank you all in advance.