Yes, right now this is absolutely the best way to build bespoke software, but it is also very wasteful. Think of all the time and the billions of tokens being burned to repeatedly reimplement apps and features. LLMS code fast, but not yet instantaneously or perfectly for complex features.
What we need is more than just OSS templates. We need fully LLM-managed "software libraries". These would be like package managers on steroids. They would be a huge hierarchy of LLM-coded modules. When you ask for an app, your LLM assembles it from the modules that already exist. If you ask for a novel feature, it codes it up and places it into the library.
So, for your VST player example. You would ask for a barebones version with just the features you need, and your LLM would assemble it for you from preexisting library modules. Then you ask for sound font support. If there is an existing sound font module, it would download it and add it into your app. If there wasn't, it would create one and put it into the library, so the next time someone asks, they can quickly get a VST player with sound font support.
This would work if all LLM contributions were not only open-source, but also public domain or something. Otherwise you'll get a mess of incompatible licences.
I have a similar experience where I’ve been learning the keyboard but didn’t like the available free options and the good paid apps had really expensive subscription plans so I had Claude build me something that runs natively on my iPad, with midi and microphone support and generates custom learning plans for midi pieces that I import.
I’m an engineer but not a software engineer and it’s been pretty interesting trying out vibe coding and seeing the barriers of entry being blown apart.
I’ve been progressing at learning the piano quite a lot faster than I expected with this. I’ve been debating open sourcing it but I’m not sure I want to take on the work of managing it