How to vet Cursor rules before using them

You're browsing awesome-cursorrules , or someone shared a .cursorrules file in Discord, or you found a repo on GitHub with rules that look perfect for your stack. Before you copy it into .cursor/rules/ , check if it actually works. Most community rules have at least one critical issue. Some are completely broken. I grabbed 4 popular rule sets from awesome-cursorrules and ran them through a linter. 100% were missing frontmatter. 75% were too long. 50% used vague language that Cursor ignores. They're good starting points, but none of them work correctly out of the box. Here's the checklist i use before adopting any rule set i find online. the 5-point vetting checklist Quick version: ✓ Does it have YAML frontmatter? (description, alwaysApply or globs) ✓ Is the body under 2000 characters? ✓ Does it cover one concern, not five? ✓ Are instructions specific and imperative? ✓ Does it conflict with your existing rules? If any of these fail, the rule either won't work at all, will waste your con