Short answer
Keep Cursor rules short. Put workflows in skills. Rules are standing instructions: they apply always, to matching files, or when the agent decides they are relevant. Skills are a folder with SKILL.md that Cursor loads only when a task matches, or when you type /skill-name. Rules say how the project should always be worked on. Skills hold jobs such as code review or release notes.
| Rules | Skills | |
|---|---|---|
| What it is | Standing instructions | One workflow, loaded when needed |
| Where it lives | .cursor/rules/*.mdc | .cursor/skills/<name>/SKILL.md |
| When it loads | Always, matching files, or when relevant | When the task matches, or /skill-name |
| Keep it | Short | The steps for one job |
Words used in this guide
- AIPM: a tool that installs and updates reusable AI instructions.
- Workflow: a set of steps used to finish a task.
- MCP: a standard way for an AI tool to connect to other tools and information.
What this means
Rules: standing instructions for normal work
A Cursor project rule is an .mdc file in .cursor/rules. Its frontmatter decides when it applies: Always Apply, Apply Intelligently (the agent reads the description), Apply to Specific Files (globs), or Apply Manually (@-mention). Rules suit coding style, project structure, required checks, and limits that should stay active.
Skills: one repeatable job, loaded on demand
A Cursor skill is a folder with a SKILL.md file, plus optional scripts, references, and assets. Cursor loads skills from .cursor/skills and .agents/skills (and ~/.cursor/skills for your own machine), and also reads .claude/skills and .codex/skills for compatibility. The agent sees each skill's name and description and loads the full file only when the task matches.
Quick way to decide
Ask: should this instruction be in context for every chat, or only for one kind of task? Every chat or every matching file means a rule. One task, such as reviewing a pull request or writing a migration, means a skill. Skills also follow the open Agent Skills standard, so the same SKILL.md can work in Claude Code and Codex. Using Claude Code too? Compare skills vs MCP vs subagents vs hooks, with the Cursor and Codex equivalent of each.
Moving from rules to skills
Cursor includes a built-in /migrate-to-skills skill (Cursor 2.4) that converts dynamic rules and slash commands into skills. Rules with alwaysApply: true or globs are not migrated because they have explicit triggers. Review the generated files in .cursor/skills before committing them.
Simple steps
- List the instructions that should apply during normal Cursor work.
- Keep those instructions in project rules (.cursor/rules/*.mdc) or AGENTS.md.
- List the longer tasks that happen only when needed.
- Create one focused skill folder with SKILL.md for each repeated task.
- Run /migrate-to-skills if you already have dynamic rules or slash commands.
- Test the rule and skill together, remove conflicting text, and use AIPM when another project needs the same reviewed skill version.
Where to go next
- Browse Cursor skills: Ready-made skills that work in Cursor. Each page shows the files and how to install it.
- How to install Cursor skills: Add a skill to your project so Cursor can find it.
- Cursor rules vs AGENTS.md: When one plain AGENTS.md file is enough, and when Cursor rules are the better fit.
FAQ
Are skills replacing Cursor rules?
No. Rules and skills solve different problems. Rules control ongoing project behavior, while skills provide reusable steps for a task. Cursor keeps both.
Where do Cursor skills go?
Project skills go in .cursor/skills or .agents/skills. Personal skills go in ~/.cursor/skills or ~/.agents/skills. Each skill is a folder named after the skill with a SKILL.md inside.
Can a Cursor project use both rules and skills?
Yes. Keep the rule short and use the skill for detailed task steps. Make sure the two files do not give conflicting instructions.
Can I use Claude skills in Cursor?
Yes. Cursor also loads skills from .claude/skills and ~/.claude/skills, so a SKILL.md written for Claude Code usually works without changes.