Short answer
Save Cursor rules as project files, package the reusable ones, and install them with AIPM when another project needs the same workflow.
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.
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.
AIPM installs into the project
AIPM can install skill files into Cursor-friendly project folders. The rule then travels with the project.
Simple steps to create and AI agent
- Pick a Cursor rule the team uses often.
- Write what the rule does in simple words.
- Add a small example.
- Publish the rule as a skill package.
- Install it in other projects 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
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 helps install the files that Cursor can use.