Team Prompt Library
LLM prompts live in random files with no version control or sharing
Your team's best prompts exist in someone's local text file. When that person is out, nobody else can find the prompt that works. People recreate prompts others already perfected. Changes happen without tracking what worked before. Collaboration means copying text into Slack. There's no approval process when someone edits a shared prompt. You can't roll back to a version that performed better. API access to prompts requires custom code every time.
About this tool
This library stores all your team's LLM prompts in one place. Creators write and edit prompts while version history tracks every change. Approval workflows let owners review edits before they take effect. Search and favorites help people find what they need. Labels organize by use case and recommended models. The API lets applications pull prompts without hardcoding.
Built with Google OAuth authentication, role-based access control, prompt ownership settings, and complete version history, ensuring collaboration through approval workflows, REST API integration, and MongoDB storage.
Teams keep all prompts in one system with full change history. When someone edits a prompt and it stops working, they can see exactly what changed and revert to the previous version. The approval workflow prevents people from overwriting each other's work without review.
Prompts used to build this app
I want to build an app called PromptHub, which will enable me and my co-workers to manage our LLM prompts, and to share them with each other and basically manage all of that. I want to have three types of users, three roles: Viewer, Creator, and Admin. An admin should have admin settings where they can manage all the users, invite new users. When they invite them, they should get an email to sign up, to set a password, and to basically access the platform that way. And the admin should be able to change the role for each user. And while inviting a user, the admin should be able to choose the role for that specific user. Actually, it shouldn't be able to set the password, but they should just get an access. And logging in should be done through Google Login. And so, basically, when a user is invited, then they get access, and they should get an email with a link to log in, and they should log in with Google. On the homepage, there should be a search bar, a list of prompts, and a toggle for favorite prompts. Next to each prompt, I should have a star that, when clicked, this prompt is labeled for me as a user as favorite. And when I toggle favorite prompts, then I should see only my favorite prompts. And if I am an editor, if I'm a creator user, I should be able to edit the prompts, and I should have a button, edit, and that should take me to an edit prompt page. There should be also a page, my prompts, which is basically the same as homepage, but only with my prompts. And I should be able to edit all of my prompts, while for other prompts, I should be able to edit only the prompts that are set to, that anyone can edit the prompt. Then, on the prompts page, there should be all the data from the prompt. The button, add as favorite, like the star, just like on the homepage. The edit button, if this user should be able to edit this prompt. And the name of the person who created this prompt. And also add the person who created it on the homepage as well. Then there should be create or edit a prompt page. On it, I should be able to add a title to the prompt, a description, the actual prompt, which is basically text. This should be like big text fields. And I should be able to add any number of labels, so there should be an input field where I can start typing and search for all the existing labels, and I should be able to add a new label if it doesn't exist. I should be able to, I should have a toggle system prompt. If I toggle it, then there should be another input field for the system prompt that should be saved as well. And then there should be a toggle if this prompt should be available in the API. Then there should be a dropdown where I should be able to set if this prompt is editable only by me, by other creators, or by other creators with my approval. If a creator edits my prompt and if my prompt is set to edit with approval, I should get an email and I should get on the approval page. On the approval page, I should see all the changes in git style that has been changed, and I should see the name of the creator who is editing this prompt, and I should be able to accept changes or decline changes. And both editing or declining, the creator who edited this prompt should get an email that their changes have been accepted or denied. And finally, on this page, I should see a history of this prompt. It should be in a sidebar. I should be able to click a button that should expand the sidebar and I should see the entire history of changes, the time when the change was made, by whom the change was made, and I should be able to click it and it should open up a pop-up with all the changes for this change and I should be able to roll back the whole prompt to this specific version. For the labels, there should be a general label where I can basically add anything, recommended LLMs labels, and recommendations to use. In recommendations to use labels, I should also be able to add any kind of recommendation. This should be the most prominent label and it should have a separate section while looking at the prompt, while general label and recommended LLMs should have just small separate sections. And finally, there should be an API, so each user should have their own API key which they should get in settings and with this API key, I should be able to get all the prompts that were set to be, that were toggled to be available in the API, for that specific user that has access to those prompts.
Please implement admin settings, inviting users and logging in with google. Also, make the email admin@pythagora.ai an admin.
I registered with admin@pythagora.ai but when I run the script, I get this error:node:internal/modules/run_main:123triggerUncaughtException(^Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/pythagora/pythagora-core/workspace/PromptHub/server/server/scripts/makeAdmin.ts' imported from /pythagora/pythagora-core/workspace/PromptHub/server/server/
Also, can you add this user into the database and remove the registration. I want to have one default admin and add all other users from that admin.
It works, here are the next few issues:
- Search doesn't work on the home page and my prompts page
- There is no EDIT button on the prompts that I created nor on the prompts that have edit permission with approval
- Add a label on the prompt page that shows if this prompt can be editable and how (with approval or without)
- When I'm on a prompt that has an open edit for creators without approval, I still have a button SUBMIT FOR APPROVAL and it tells me that my edits were sent for approval while in reality the edits were applied right away (which is supposed to happen) - please change it so that these prompts say "Save"
- I'm able to see the versions but when I click on one, I don't see any changes. Please fix this as well.
Editing of prompts and permissions doesn't work. I'm able to edit, as a creator, any prompt regardless if it's set to only me or creators with approval. If the permissions are only me, only the creator who created the prompt should be able to edit it, and if the permissions are set to creators with approval, then creators should be able to submit the edit, but the original creator of the prompt should get an email on which they should be able to review the changes and approve or decline them. And after that, the editor should get an email as well if their changes were accepted or denied.
Ok, this is great! It's starting to take shape. Here are a few outstanding issues:
- Rollback is visible even when editing is disabled - please make it so that only a user who is allowed to edit a prompt has the ability to roll back the prompt to a previous version
- Settings of a prompt (EDIT PERMISSIONS and API ACCESS) should only be changeable by the original creator, no one else. Please change.
- Rolling back doesn't work - it throws an error.
Please check if the API is implemented, and if not, implement the ability to get prompts over the API. Make sure that the authentication happens over the API key, so if the API key is correct, we should be able to fetch the prompt. If the API key is incorrect, we shouldn't be able to fetch it. And also, with the API, we should get only the prompts that are visible to that user with that API key.
Don’t Miss Out
