Hey, ran into something and curious if others have felt this too. I used the ICM method to build a tool. Staged pipeline, each step fed the next, worked great for getting the thing built. But now I'm realizing ICM feels designed for building fresh. If I want to build the same app for a different user, running the pipeline again makes sense. But if I want to edit the existing app, the pipeline docs are useless. They're stale and the agent has no efficient way to navigate the actual codebase. You need a completely different approach for editing. Less staged pipeline, more routing the agent around the live code so it knows where everything is. Has anyone figured out how to handle this transition? From ICM build mode to edit/iteration mode? Do you build an ICM around the edit/iteration mode as well ?

There are two skills in Claude that I use over everything else that have been really successful for me. I love the folder system here and I use something similar just to keep things organized. As I'm sure most people have heard of Superpowers and I think it's good to a point. Superpowers is good at brainstorming and asking me the questions I didn't consider but it's bad on execution. That's where GSD or Get Shit Done comes in. It can take the plan from Superpowers, break it down into Phases and Waves and then you verify at every checkpoint to make sure a certain feature works. This effectively allows me to "one-shot" apps and make sure it works along the way. The part of the stack that I don't have nailed down yet (leaning into my cyber security background a bit) is security and just trying to make sure we cover stuff like prompt/code injection for example. Does anyone else have a similar stack or different process?

Inspired by @Curtis Hays, I finished an experiment that I had started a few weeks ago. I started my company as a local web design agency in 2014. I've pivoted a few times since, where our core offer is that of Fractional CMO services, but we still do some agency type work for existing clients, friends, and family. I was ready to throw in the towel on web builds just because they take so much time and I hadn't cracked the code on building sites with ongoing content. I finally got it this evening! We've gotten good at building unique sites using Claude with next.js, files live in github, website runs on vercel. This evening I was able to get a headless WordPress environment where I can add/edit/delete content, but the design still lives in Vercel! I realize this might seem like a small thing for some, but it's a ginormous win for the 8 SIGNAL team :D It's gonna save us sooooooo much time rebuilding from next.js to Elementor. Huge shoutout to Curtis. By sharing his win, he inspired me to dig further into this and figure it out! Here's the site that was previously just a "static" site on vercel, now all the content is coming from a wordpress install: https://century-rentals.vercel.app/ P.S. If you have a better way of managing websites that require a CMS and SEO/AEO, don't hold back. I won't be deflated. I'm always looking for ways to improve and do things better. P.P.S. Website's for a buddy, and still not finalized yet, so I'm taking some liberty to mess around with him about baseball because he knows less than I do, and I don't know much LOL!