Cursor Rules vs Skills: Official Docs Explained (2026)

Per Cursor's own documentation, a rule (.cursor/rules/*.mdc) is a standing constraint that loads always or by glob, a skill (.cursor/skills/*/SKILL.md) is a playbook the agent opens on demand, and a command (.cursor/commands/*.md) only runs when you type it — see Cursor's docs on commands linked below for the source. Rules constrain, skills teach, commands are typed. Don't put the same text in two places. Last updated 2026-10-31 by Rakshit Yadav.

Rules vs skills vs commands at a glance

RulesSkillsCommands
LoadsAlways, or when a glob matchesWhen the task matches the description, or when invokedOnly when you type it
Triggered byCursorThe agent or youYou
Folder.cursor/rules/.cursor/skills/<name>/SKILL.md.cursor/commands/*.md
Best forShort bans and conventionsLonger playbooksRepeatable multi-step jobs

Official reference: Cursor docs: Commands; check the current Cursor docs for rules and skills, which are still changing. Cursor has also been moving slash-command-style workflows toward skills, with a /migrate-to-skills command in recent versions (verify it exists in your Cursor build). Commands and skills overlap most; see Cursor Skills vs Commands.

New to skills? Start with Best Cursor Skills in 2026.

The one-line difference

Rules (.cursor/rules/*.mdc) are passive. They fire always, or when a glob matches. Skills (.cursor/skills/*/SKILL.md) are playbooks the agent loads when the task matches the description, or when a command points at them.

Cursor's own docs now steer extension toward skills so the window stays lean. Rules remain for hard prohibitions and path-scoped law.

Use a rule when

  • The instruction must apply to every turn (read CURSOR.md, tenant from session).
  • The instruction should fire only on app/api/** or *.sql.
  • It is a ban, not a manual: no any, no raw SQL in the route.

Use a skill when

  • The standard is longer than a screen: Stripe webhooks, RAG chunking, on-page SEO.
  • You only want it loaded on matching work.
  • An agent or command should open a named playbook.

Examples: Stripe payments skill, on-page SEO skill, Next.js App Router skill.

Do not duplicate

If a rule and a skill disagree, the rule wins and you have a mess. If they say the same thing, you paid twice in tokens. AgenticKit keeps a short always-on core and puts the manuals in skills. Grade a fat dump with the Rules File Grader before you migrate it.

Related pages

Frequently asked questions

  • Are Cursor skills replacing rules?
    No. Skills are preferred for on-demand playbooks. Rules still own always-on and glob-scoped constraints.
  • Should I migrate all .mdc files to SKILL.md?
    Only the long ones. Keep tenant-from-session and error-envelope rules as rules.
  • What is the difference between a Cursor command and a skill?
    A command is a markdown workflow you trigger by typing / and its filename. A skill is a SKILL.md playbook the agent can load on its own when the task matches its description.
  • What does /migrate-to-skills do?
    It is a Cursor command that has appeared in recent versions for converting older rules and commands into skills. Behavior may change, so read the current Cursor docs and review the generated SKILL.md files before committing them.
  • Where do rules, skills and commands go?
    Rules in .cursor/rules, skills in .cursor/skills/<name>/SKILL.md, commands in .cursor/commands.

See the 61 skills

The playbooks live on the Cursor Skills pillar. Rules stay short on purpose.