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?

On April 10 I was trying to clean up my Instagram.Tighten the cover graphics. Build a repeatable system. Stop redesigning the same template every week. A one-afternoon job. What actually happened was the first real test of an architecture I had been sketching for writing work — and I tested it on design. I built a sandbox, gave it a governing file, separated references from working material, wrote one clean brief… and let it run. Fifty covers came back in minutes. Same palette. Same typography. Same visual language. None off-brand. That was the moment something shifted. Not because of the output — but because of what it proved: Once an architecture is clear enough, the question is no longer “what can I delegate?”It becomes “what is now worth building?” In 21 days, that small test turned into: - Three working teams (orchestrator, content, design) - Four books shipped or shippable - A new website - Two additional teams already scoped Same operator. Same hours in the day. For those who asked about mindset and process — this is the real answer: 1. I stopped thinking in prompts and started thinking in systems.The model is not the asset. The structure around it is. 2. I separated thinking from doing.The orchestrator doesn’t write. It reads, structures, briefs, and validates.The workers execute. They don’t improvise outside their lane. 3. Everything moves through briefs.No direct “do this” requests. Every handoff is:task → context → scope → acceptance → return checklist.That alone removed most iteration cycles. 4. Context is layered, not dumped.Reference material lives separately from working material.The model doesn’t have to “figure out what matters” — it’s already decided. 5. The human sits outside the system.Not inside prompting.Outside — validating outputs and deciding what ships. The clearest proof this wasn’t theory came from the hardest task I’ve ever tried to coordinate: Mapping TCM meridians, Thai Sen lines, and Anatomy Trains on the human body — in one consistent visual language.

Signed before the tool is finished. Signed before the new company is even incorporated. I'm building a Marketing Stack for my SaaS company and before I was finished with Phase 1 of the seven planned phases I was thinking about several people who had talked to me recently about their pain in the same area. Made the call, explained the idea, addressed their pain, and signed the deal. If you approach what your are building as a system that can be deeply customized for each user, then you have a product that people will want. Build it to solve your problem but remember that the customization, the personalization, the flexibility, and the agility of what we can build with AI as the newest abstraction layer of software development is what makes what we are doing here better than what SaaS can do. SaaS is a cookie cutter template that the r has to cram themselves into. What we can build is deeply personalized software solutions.

Wanted to share that today my boss came to me and asked seriously "Is this really possible?" and I was able to confidently say absolutely and we can make it whatever we want. Probably gonna be some discussions about what needs to go on the website but really happy that after last week's proof of concept website we're actually gonna move forward on our branding, nice end of the week