agent-doctor / rules
Cursor rule4 starsChanged 19 days agoMITView on GitHub
Diagnose chat error screens with the experience spec, not a new error-string branch
We split this chat-experience.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When a chat screenshot shows a raw log, a script, or a duplicated failure, follow docs/zh-CN/chat-experience.md.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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: Diagnose chat error screens with the experience spec, not a new error-string branch alwaysApply: true --- # Chat experience When a chat screenshot shows a raw log, a script, or a duplicated failure, follow `docs/zh-CN/chat-experience.md`. - One fact lives on the surface that already owns it (the tool row, the confirm card, or a single failure sentence). - The original text stays, collapsed by default. - Strip terminal color codes before display, including leftover `[31m` / `[0m`. - Classify a runtime log by shape (color codes, or a timestamp plus a severity). Do not add a branch for one error string, app, or folder.
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 3,978 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/beginner-users.mdcCursor rule
- .cursor/rules/desktop-dev-frontend.mdcCursor rule
- .cursor/rules/github-release-packaging.mdcCursor rule
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.