-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add template system for promt #3
Comments
To make the prompt easier and clearer editable, there is now the option to format the prompt as Markdown, plus a script that removes line breaks and turns underlined headings into ones with ##. The Markdown file, e.g. This creates the new file You can find the script in for example, out of ....
... this, which you can then easily insert into the
|
You can find the prompt for OpenAI currently in the file
personas.json
as a single line:https://github.com/ClemensGruber/climart_gptree/blob/043834c07826a98d9358834c619a38ab73e98fb4/personas.json#L27-L29
A single, very long line is not good readable, editable and maintainable.
But due to JSON restrictions paragraphs or line breaks are not possible for better structuring.
Fast workaround
At GitHub you can use the raw view instead of the normal UI to show the code as text in the browser, normally the browser will auto wrap long lines.
In case you are editing at GitHub you can switch from "no wrap" to "soft wrap" in the drop down option top right at Git's online editor.
At your local editor there should be a similar function for auto wrapping. In Windows' notepad you will find it under "view". With nano on Linux the shortkey Esc + $ will do soft wrapping. For the RasPi heed this hint in case nothing happends after the keyboard shortcut.
Make prompts better maintainable
Independently from the workaround above we need better opportunits to manage promps. We have often same code blocks for
So it would be nice to have them as single
*.txt
for easy editing and maintaining, e.g. comparable to the audio files inprompts/
asformal-role.txt
,formal-output.txt
,topic-context.txt
,project-info.txt
...[persona]-individual-propt.txt
and you can specify in/personas.json
(?) what*.txt
files to include for the respective tree / persona.The text was updated successfully, but these errors were encountered: