> Right now I'm working on a declarative UI framework which can help me along here

After your first para, I was about to suggest exactly that (well, maybe not writing your own). I find that frameworks (both front-end and back-end) constrain the LLM's choices and result in both sensible defaults and improved consistency.

Of course, you will immediately hit the problem all frameworks have: customer requirements that the framework components don't quite meet.

Still, great for RAD.

Can you elaborate on what frameworks you've used? and how they've helped

Probably one of those things where it's best to try it yourself, because I think anything that constrains the LLM is an improvement.

Think up a simple CRUD problem (lets say a book database - Book *-* Author, Book 1-* Publisher, Book 1-* Shelf). Write a loose markdown spec, and have the chatbot one-shot it in [language of choice]. Then do the same thing, but tack "build it in Filament/Avo/Django/AdonisJS" on the end.

I'd be interested to see if your results match mine - everything's just more consistent, and smoother, and you start getting freebies like autocomplete. The framework acts as guardrails and the LLM has to make fewer choices, so less of the token budget goes on bikeshedding.