Short answer
Store important prompts as named files, explain their input and output, review changes in pull requests, and give shared prompts a version. Package prompts that are used in several repos instead of copying them.
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.
- Workflow: a set of steps used to finish a task.
- 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
Treat important prompts like project settings
A prompt can change generated code, tests, or documents. Put important prompts near the project, use clear file names, and let the team review changes.
Record what good output means
A prompt file should say when to use it and what information it needs. It should also describe the result. Add a small example when possible.
Use packages across repositories
Git handles history inside one repo. AIPM adds a package name, version, and install command when the same prompt workflow is needed in several repos.
Simple steps to create and AI agent
- Move repeated prompts out of chat history.
- Give each prompt one clear job and file name.
- Add expected input, output, and a small example.
- Review prompt changes in pull requests.
- Package prompts that need to stay aligned across repos.
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
Can Git version AI prompts?
Yes. Git records prompt changes, authors, review comments, and earlier versions just like other text files.
When is a prompt package useful?
Use a package when a prompt is important, reused by a team, or installed in more than one repo.