Short answer
Save important prompts in project files and record their changes with Git. Put shared prompts in packages with clear version numbers.
Words used in this guide
- AIPM: a tool that installs and updates reusable AI instructions.
- Package: a named group of files that people can install and update together.
- Repository or repo: a project folder whose changes are saved and tracked.
- Git: a tool that records file changes so people can review or undo them.
What this means
Move prompts out of chat
Chat history is not a good source of truth. If a prompt matters, save it as a file in the project.
Review prompt changes like code
A small prompt change can change AI output. Use pull requests so teammates can read the change before it spreads.
Use packages for shared prompts
If many projects need the same prompt, publish it as an AIPM package. Then each project can install a clear version.
Simple steps to create and AI agent
- Create a folder for AI files in the repo.
- Add the prompt, its purpose, and examples.
- Commit the file to Git.
- Review changes before merging.
- Publish shared prompts as AIPM packages.
Where to go next
If you want to try this in a real project, start with the install guide, then read how to use AIPM. If you want to share your own workflow, read the publishing guide.
FAQ
Why not keep prompts only in a shared document?
A shared document is easy to read, but it may not match the project. Git keeps the prompt near the code that uses it.
When should I publish a prompt package?
Publish it when the prompt is useful in more than one project or for more than one teammate.