add descriptions and explicit empty globs in rule frontmatter

[randyoyarzabal]

• Set non-empty description on each .mdc rule so Cursor can show clearer labels and match tasks to the right rule.
• Use globs: [] for an explicit “no path filter” list and valid YAML.

Changes

File	Update
using-flags.mdc	description: focus on flag evaluation; globs: []
implementing-launchdarkly.mdc	description: SDK setup/config; globs: []
troubleshooting-launchdarkly.mdc	description: SDK/flag debugging; globs: []

Rule bodies unchanged.

How to verify

Open the repo in Cursor → Settings → Rules → confirm each project rule shows the new description.

[devopsdina]

Hmm, I am wondering how the brackets work here? I think it is supposed to be blank so it applies to all files (since we aren't specifying a pattern).

cursor docs state

Glob patterns: Team Rules support glob patterns for file-scoped application. When a glob pattern is set (e.g., **/*.py), the rule only applies when matching files are in context. Rules without a glob pattern apply to every conversation.

[randyoyarzabal]

Hmm, I am wondering how the brackets work here? I think it is supposed to be blank so it applies to all files (since we aren't specifying a pattern).

cursor docs state

Glob patterns: Team Rules support glob patterns for file-scoped applications. When a glob pattern is set (e.g., **/*.py), the rule only applies when matching files are in context. Rules without a glob pattern apply to every conversation.

Yeah, I saw. The reason I did that was following the cursor's recommendation to make it a valid YAML format. But based on the docs example, it's safe to drop this. I will remove the glob: [] and revert back to glob:, I think the description change is at least valid.