Solution for Managing LLM Prompts
For those of you working with LLMs, how do you manage the growing sprawl of prompts such as system prompts, templates, chains, and experiments across projects? I am looking for practical ways or tools to organize, version, and search prompts so they are easy to refine and reuse, instead of keeping them scattered in notes or GitHub gists.
1 comments
This is a very fast moving environment, my prompts from 2024 were created for that reality, and should be removed later in 2025. For example all the CoT techniques are anachronic now.
But this also means a new architecture of the surrounding app, for example instead of chat UX we want to have more of async processing, when the focus is to do the job correctly instead of responding to the user with some message.
So the solution is to assume that at some point we will need a major rewrite, because current architecture does not allow us to make use of the modern model potential, and modifying prompts is not enough.
So the solution is to assume that at some point we will need a major rewrite, because current architecture does not allow us to make use of the modern model potential, and modifying prompts is not enough.