Short answer
Save Cursor rules as project files, commit them to Git, and package reusable rules with AIPM when other projects need 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.
- 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
Rules should be reviewable
Cursor rules can change how AI suggestions behave. A team should be able to read and review those rules before they spread.
Git shows what changed
Git shows the team every change to a rule. People can discuss the change and undo it if the AI starts giving poor answers.
Reusable rules can become packages
Some rules are useful in many projects. A team can publish one rule with AIPM and then install it in each project.
Simple steps to create and AI agent
- Create a clear folder for Cursor rules.
- Use names that explain the task.
- Commit the rules to Git.
- Review rule changes in pull requests.
- Package rules that are useful in many projects.
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 Cursor rule be shared?
No. Keep project-only rules in that project. Share rules that help many repos.
Can AIPM install Cursor rules?
AIPM can install files made for Cursor. The package shows which files it contains.