Short answer
Put shared instructions in one AIPM package. Install that package in each project. Keep details that belong to only one project in that project. This gives every project the same basic rules without manual copying.
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
Copied files soon become different
A copied instruction does not get later updates. After some time, each project may have different rules even when the team expects them to match.
Split shared and local instructions
Shared instructions should cover common review, testing, security, and documentation work. Repo-specific files should cover local commands, architecture, and limits.
Install a reviewed version
An AIPM package can include files for Cursor and Claude targets. Each repo installs a named version, so updates are visible and can be reviewed before they spread.
Simple steps to create and AI agent
- List the instructions repeated in several repos.
- Remove private and repo-specific details.
- Create target files for the AI tools your team uses.
- Publish the shared files as an AIPM package.
- Install and update the package through normal Git review.
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 every repo use exactly the same instructions?
No. Share the common base and keep local commands, architecture, and product rules in each repo.
How do teams keep instructions the same?
Keep the shared instructions in one package with a version number. Update each project from that package instead of copying files by hand.