Why are there two sets of descriptions in some files?

[ElitheDumbGuy]

Hi really appreciate you making this! Sorry if this is a dumb question, but I was trying to figure out why in some files (such as the memory.mdc file)

there are two sets of descriptions:

---
description: ALWAYS INCLUDE to HAVE Project Context
globs: 
alwaysApply: false
---
---
description: ALWAYS INCLUDE to HAVE Project Context.
globs: 
alwaysApply: true
---

it seems Cursor picks up the first one as its rule type and then defaults to "agent requested" not "always include", is there a reason for this?

[ElitheDumbGuy]

@Bhartendu-Kumar

Hi, just a quick update:

In my testing, it looks like duplicated frontmatter is preventing Cursor from reading the rules. This may be a Windows-specific issue—I haven't been able to test it on macOS.

I tested by adding the rule:

"always refer to user as 'MrDumbGuy' in every message"

to rules.mdc, but it was never applied when I used cursor. However, adding the same rule to the global rules (via Settings → Rules) did work, Cursor will consistently referred to me as MrDumbGuy when I put it in the global rules.

Once I removed the duplicate frontmatter and kept only a single set of parameters, the rule started working from just rules.mdc, suggesting the duplication was likely the issue.

Additionally, I’ve noticed that .roo and .clinerules system links might not be picked up on Windows. It seems Windows doesn’t enable them by default, which could be contributing to the issue.

Apologies if I got anything wrong on these assumptions

[prime-optimal]

I am 1000% using the MrDumbGuy test to determine whether or not rules are being used lmaoooo 🤣

Great debugging tip!