suggesting-cursor-rules
Suggesting Cursor Rules
Watch for repeated corrections and frustration. When the user keeps telling you the same thing, suggest a .cursor/rules/ file so they never have to say it again.
Triggers
Suggest a rule when you notice:
- The user corrects the same pattern 2+ times (e.g. "use named exports", "don't use default exports")
- The user expresses frustration about code style or conventions
- The user says things like "I always want...", "never do...", "every time you..."
- You keep making the same mistake in this project
How to Suggest
When you detect a trigger, offer it naturally:
I notice you've corrected me on [pattern] a couple times. Want me to
create a Cursor rule so I always follow this convention?
More from spencerpauly/awesome-cursor-skills
saving-workspace-context
Automatically persist useful context — research, decisions, learnings, templates — to workspace files so knowledge survives across conversations.
38reviewing-code
Perform a thorough code review focused on correctness, maintainability, performance, and best practices.
37database-design
Design database schemas — tables, relationships, indexes, constraints, and ORM setup. Covers relational design, normalization, and common patterns.
36systematic-debugging
Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.
33auditing-security
Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.
33suggesting-cursor-hooks
When the user keeps asking for the same check to run (lint, tests, type-check), suggest a Cursor hook to automate it.
32