Short answer
Save Cursor rules as .mdc files in .cursor/rules, commit them to Git, and review changes in pull requests. For task-style instructions that many repos need, use a skill that AIPM can install.
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 instructions are useful in many projects. AIPM does not package Cursor rules today, but a task-style instruction can become a skill that AIPM installs into each project at a pinned version.
Simple steps
- Create a clear folder for Cursor rules.
- Use names that explain the task.
- Commit the rules to Git.
- Review rule changes in pull requests.
- Turn task-style rules that many projects need into a skill.
Where to go next
If you want to try this in a real project, start with how to use AIPM and the command reference. 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?
Not today. AIPM installs skills (SKILL.md folders); Cursor rules packaging is planned. Cursor loads skills installed with --target claude or --target codex.