agent-doctor / rules
Cursor rule4 starsChanged 19 days agoMITView on GitHub
Dev rebuilds must load the live Vite page, never the old packaged frontend
We split this desktop-dev-frontend.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Do not run cargo build -p agent-doctor-desktop with default features, and do not relaunch that binary.
- Very specific: line 13
Do not replace the open dev app with a freshly embedded build.
≈ “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: Dev rebuilds must load the live Vite page, never the old packaged frontend alwaysApply: true --- # Desktop dev frontend A normal `cargo build` of the desktop app embeds `desktop/dist`. That page is an old package. The window then rolls back to a previous UI. Do not do this while developing. - Rebuild the running dev app with `npm run tauri:dev:personal` in `desktop/`. That command uses `--no-default-features` and loads `http://127.0.0.1:1420`. - A hand build is allowed only as `cargo build -p agent-doctor-desktop --no-default-features`, and only while Vite is already serving port 1420. - Do not run `cargo build -p agent-doctor-desktop` with default features, and do not relaunch that binary. Default features turn on `custom-protocol` and bake in `frontendDist`. - Do not replace the open dev app with a freshly embedded build. The source under `desktop/src` is the page the user is looking at.
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/chat-experience.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.