Skip to lesson
Exit
Project Rules and AGENTS.md1 / 2

2 min lesson

Put Rules to work on one real case, and keep one proof point

Put this idea into your own words: "Start with this check: The rule is specific and easy to verify."

Step 1 of 2

The job: the correction becomes a durable instruction instead of repeated prompt text. Start with this check: The rule is specific and easy to verify. Keep it small enough to check the result yourself instead of taking the summary on trust.

Rules that load before the edit

0:37 · narrated
Read this demo as text
  1. Open Cursor Settings, Rules. search-scope is a project rule — it only applies under the file path src/components/search.
  2. Close Settings and open Agent chat. The prompt names the search-scope rule and AGENTS.md so you can see whether the agent loaded them.
  3. Send it. Watch the agent load search-scope and AGENTS.md, then edit EmptyState only — durable instructions beat retyping the same correction.
Watch once: Project Rules in Settings, then an agent run that loads search-scope and AGENTS.md before editing.

Practice next: Now do the module workflow: turn a repeated correction into a checked-in rule and test it with a small run.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.