Appearance
SEC380 / CURSOR-DESCRIPTION
SEC380 flags Cursor rule markdown when frontmatter is present but does not include a non-empty description.
Why It Matters
Shared .mdc rule packs are much easier to review, route, and maintain when each rule explains its purpose. Without description, reviewers have to infer intent from the body alone, which makes broad or global rules harder to audit.
This rule lives in the explicit guidance lane because the issue is reviewability and shared-config quality, not a headline exploit-style security claim.
Trigger Shape
The rule triggers only when all of these are true:
- the file is a detected Cursor rule surface
- frontmatter parses as a mapping
descriptionis missing or empty
Clean Cases
These stay clean:
- rules with a non-empty
description - non-Cursor markdown
- fixture-like examples under test or fixture paths
Example Trigger
md
---
alwaysApply: true
---Safer Example
md
---
description: Project-wide coding conventions
alwaysApply: true
---How To Fix
Add a short description that explains when the rule applies or what behavior it enforces. Keep it concise so shared rule packs remain easy to review.