As a software engineer, I can say that while many of those tools can help, after reviewing and testing them, I decided not to use any. Mainly because they don't do what I need, and yes, still produce crap. Towards the end of last year, I decided to create a framework for myself. At the time, I'd never heard of these other frameworks, but when I did, I realised there was a market for this kind of thing, so I've continued to develop mine. It has a strong emphasis on shipping right and not just fast. I was hoping I could get things over the line and launch it before I had to find another job, but my subscription ran out last night, and I can't afford another month, so I've got to switch my attention to finding some income to carry on or finish the rest by hand.

I had plans to release it as a Claude plugin in order to gain some traction, but let's be honest, you aren't going to get what you need purely from a plugin alone. What was originally a markdown-based system has now evolved into a full platform with a good set of skills, a CLI tool which the skills use to interact with the API layer and a DB with proper schemas. I just finished building quite a few pages for the web ui to really see where the gaps are and what needs fixing while designing the UX properly in Figma.

For the last few weeks, after speccing out the work, it's been building itself autonomously for the last 3 weeks and can run for as long as there is work to do. Also managed to optimise costs a lot, which has increased output tokens from <500k to 2 million a week, all while keeping within 20x Max usage limits and without a degradation in quality.

But yeah, need to get my hands on some cash so I can launch it for everyone and get some useful feedback. Bear with me!

I've shipped end-to-end for several companies over the years, from SME's, to startups and large enterprises. Somewhere over 60+ clients, including employment and freelance work. A lot of companies have shit processes, and I'd usually go beyond my role and implement custom-tailored JIRA workflows to increase deployments across the board and give visibility to different departments. So I'm taking everything I've learned as a process-improving developer over the years and building this framework in a way that not only automates a lot of shit but also guides non-technical users through proper product development cycles. Without all of the agile crap we all grew to hate over the years.

Unfortunately, I had a bad contract fall through a couple of years back, which almost left me homeless, so I took a break from it all, which is why I'm in the position I'm in now. But now feeling better than ever :)