Short answer
Keep important AI agent instructions as files in the repo. Review them in pull requests and package shared instructions with AIPM.
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.
- Config: settings that tell a tool how to work.
What this means
Instructions are part of the project
AI tools affect how work gets done. Their instructions should be visible to the team, just like tests, docs, and config files.
Git gives you history
When an instruction changes, Git shows who changed it and why. That makes it easier to fix mistakes later.
Packages help across projects
If the same instruction is useful in many repos, package it. Then the team can install it instead of copying it again and again.
Simple steps to create and AI agent
- Create a clear folder for AI instructions.
- Use simple file names.
- Explain what each instruction is for.
- Review changes in pull requests.
- Package shared instructions with AIPM.
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
Should all AI instructions be public?
No. Keep private business details and secrets out of public packages.
Why put AI instructions in Git?
Git makes the instructions easy to review, update, and roll back.