Use Cursor Rules for Conventions and Skills for Repeated Workflows

A project rule attaches instructions to relevant files or chats. A skill provides a procedure you can invoke for a specific task. Keep the configuration small enough that the team can test each behavior independently.

Worked example

A project rule that applies in every chat

---
alwaysApply: true
---
Edit source files. Rebuild files under generated/ from their source when needed.

A skill for a release note draft

---
name: release-note
description: Draft a short release note from a reviewed change.
---
Read the supplied change summary. State the user-visible behavior, then list one limitation if the evidence supports it.

Steps

  1. Save the rule example as .cursor/rules/generated-files.mdc so the constraint is available in project chats.
  2. Save the skill example as .cursor/skills/release-note/SKILL.md. Invoke the skill from a fresh agent chat when you want to draft the note.
  3. Test an ordinary task that touches generated output and a second task that explicitly requests the release-note skill. Check that each result follows the relevant instructions.

What to check

  • Check that the rule appears in Cursor's project rules list and the skill appears under Skills. A correctly written file in the wrong folder can still be undiscoverable.
  • Agent instructions guide the model. Use a build or CI check to enforce generated-file policy.

See the Cursor tool profile

References