Why provide a hard coded list of message and not collect the system messages defined by the application ?

What I had in mind when opening the issue was for us to leverage the awesome prompt library available in https://github.com/danielmiessler/fabric/tree/main/patterns

@jmartisk what's the status of this one?

The status is that I would like somebody to chime in and say if this is worth pursuing further this way, or some other way, or not at all :)

Oh and yeah, regarding https://github.com/danielmiessler/fabric/tree/main/patterns
The problem is that the prompts contain placeholders. In the UI, it's not very pleasant to work with, as one has to read the prompt and manually replace all placeholders, so I'm not super excited about that :(

Unless we also come up with a way to allow pleasantly defining values for placeholders, it doesn't seem very useful.

There's also the question of whether pre-defined prompts from some kind of library really make sense in this context, while the main point of the UI page is to allow easy testing of RAG and tools of the application. It's for working with the application, not experimenting with a library of prompts that have no relation to the app.

I am not saying that we must have those prompts in this screen, but there should somewhere that we surface those prompts to users as they are super helpful