Skip to content

Cursor Rules vs Skills

Standing conventions → Rules. Repeatable workflows/scripts → Skills. Simple project notes → AGENTS.md. Long reference material → local Markdown you @-mention.

By SundryardLast reviewed 15 Sept 2026How we source claims

Visual Studio Code editor window — stand-in for Cursor IDE customization
VS Code on Windows (Wikimedia). Cursor is a VS Code fork; image is a stand-in for the editor UI. · Miguelferig · Wikimedia Commons
Visual Studio Code editor window — stand-in for Cursor IDE customization
VS Code editor (Wikimedia). Cursor is a VS Code fork — Rules, Skills, and local Markdown are how you shape Agent behavior after @Docs.

Cursor Rules vs Skills

Pick what you need. Standing conventions belong in Rules. Repeatable workflows belong in Skills. Long reference text stays in local Markdown you `@`-mention. Simple project notes can live in AGENTS.md.

Cursor docs checked 2026-09-15.

Replacing @Docs? See What happened to @Docs in Cursor?

What are you trying to encode?

Use Rules

Rules are for persistent instructions that should apply Always or on path globs every session.

Do now: Add a short `.cursor/rules/*.mdc` rule. Prefer Always Apply or globs. Keep it under a few hundred lines; point at files instead of pasting whole style guides.

Example: “Never commit `.env`. Use named exports in `src/components/**`.”

Side-by-side

MechanismPurposeWhereWhen it applies
RulesPersistent instructions the Agent includes when the rule applies.Project `.cursor/rules/*.mdc`, User rules, Team rulesAlways, by glob, or manually — depending on the rule type
AGENTS.md / CLAUDE.mdPlain markdown project instructions without rule frontmatter.Repo root (and nested folders); CLAUDE.md documented for Cursor CLILoaded as agent instructions; more specific nested files win
SkillsPortable packages (`SKILL.md`) for domain workflows the agent loads when relevant or via `/skill-name`.Skill folders with `SKILL.md`, optional `scripts/`, `references/`, `assets/`When relevant, or when you invoke `/skill-name`
Local MarkdownReference files in the repo you `@`-mention or let the agent open — not a separate Cursor product surface.`docs/`, guides, OpenAPI dumps, design notesOn demand when mentioned or opened — not always-on context
  • Rules example: Always use named exports under `src/components/**` (glob rule).
  • AGENTS.md / CLAUDE.md example: How to run and debug the three main services in this monorepo.
  • Skills example: Deploy to staging with `scripts/deploy.sh` and a when-to-use description.
  • Local Markdown example: Keep the API reference in `docs/api.md` and `@docs/api.md` when changing endpoints.

Sources

Local Markdown is workspace files plus `@` mentions — not a separate Cursor product page. Commands are a different Customize surface and are out of scope here.

Next

More in this topic →