Short answer
Save Cursor rules as .mdc files in .cursor/rules and share them through Git. AIPM does not install Cursor rules today; if a rule is really a repeatable task, turn it into a skill and install that 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.
- Workflow: a set of steps used to finish a task.
- Git: a tool that records file changes so people can review or undo them.
What this means
Cursor rules should be visible
If a rule changes how Cursor works, the team should be able to read it. Keep rules in files, not only in a private note.
Reusable rules should have a name
A rule for code review, test writing, or release notes can become a package. A name makes it easier to find and install.
Where AIPM fits
AIPM installs skills, not rules (rules packaging is planned). Cursor loads skills from .claude/skills and .agents/skills, so a skill installed with aipm add --target claude or --target codex works in Cursor and travels with the project. For sharing Claude skills across a team, see how to share Claude skills with your team.
Simple steps
- Pick a Cursor rule the team uses often.
- Write what the rule does in simple words.
- Add a small example.
- Share always-on rules through Git; turn task-style rules into a skill.
- Install the skill in other projects with AIPM (--target claude or --target codex).
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
Can Cursor rules be different per project?
Yes. Keep project-specific rules in that project. Package only the rules that are useful in many projects.
Does AIPM replace Cursor?
No. AIPM installs versioned skills that Cursor, Claude Code, and Codex can load. It does not install Cursor rules.