|
|
|
|
|
|
by rrandall
671 days ago
|
|
|
Markdown w/ string replacement seems fine to me. JSON works well for when you need to structure the rest of the config along with the prompt. I assume you could combine markdown + JSON. You will start running into issues with referential integrity, etc. with just a plain text file though. You may also want outside collaborators other than devs. So you might need a more involved prompt management system on top of that. What feels error prone to you? |
|
|
The string replacement feels error prone, and ideally we would have better methods for reviewing full prompts beyond running the code.
I’m imagining something like Storybook[0] but for our prompt management.
Something that renders the markdown and can do realtime replacement across the different paths we use for generating prompts.
For context, we reuse many “wrapper” prompts and then have a few context-specific replacement prompts that are nested within the larger prompts. It works OK for one level of depth, but multiple levels make it hard to interpret from the raw code itself.
During dev/runtime, we have some color coordination for the different levels, but again, ideally this was built into the way we store/version our prompts.
We’ve looked into a few different prompt analytic/versioning tools, but they all seem too simple for our use-case.
[0]https://storybook.js.org/