DeskHog / rules
Cursor rule493 starsChanged 20 months agoMITView on GitHub
Fixing problems, recovering from failures
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- .cursor/rules/about-project.mdcCursor rule
- .cursor/rules/application-structure.mdcCursor rule
- .cursor/rules/code-generation.mdcCursor rule
The file
We split this troubleshooting.mdc into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
When troubleshooting, writing new code is the final step, not the first.
- Distinctive: line 9
Instead, think of up to five root causes of a failure, then narrow down to the most likely one or two.
- Distinctive: line 11
Only after providing a detailed plan for remediation will you write new code.
- Distinctive: line 13
Do not invent functions or properties on external libraries that don't actually exist, since this won't actually solve the problem.
- Distinctive: line 17
If USB operations falter, this command can reset the whole USB subsystem:
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Fixing problems, recovering from failures globs: *.cpp, *.h alwaysApply: false --- When troubleshooting, writing new code is the final step, not the first. Do not randomly try new code. Instead, think of up to five root causes of a failure, then narrow down to the most likely one or two. Only after providing a detailed plan for remediation will you write new code. Do not invent functions or properties on external libraries that don't actually exist, since this won't actually solve the problem. Switching away from Arduino framework is never a viable strategy. If USB operations falter, this command can reset the whole USB subsystem: sudo pkill -f "usb|serial|uart"; sudo pkill -f tty; sudo killall -STOP usbd; sleep 2; sudo killall -CONT usbd;
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.