scholaraio / rules
Cursor rule585 starsChanged 3 months agoMITView on GitHub
ScholarAIO project instructions and research workflow router
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 repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- academic-writingSkill
- arxivSkill
- auditSkill
- backupSkill
- bioinformaticsSkill
- citation-checkSkill
- citationsSkill
- documentSkill
- drawSkill
- enrichSkill
- exploreSkill
- exportSkill
- graphSkill
- gromacsSkill
- importSkill
- indexSkill
- ingestSkill
- insightsSkill
- lammpsSkill
- literature-reviewSkill
- metricsSkill
- nature-workflowSkill
- openfoamSkill
- paper-guided-readingSkill
- paper-writingSkill
- patent-fetchSkill
- patent-searchSkill
- posterSkill
- publishSkill
- quantum-espressoSkill
- renameSkill
- research-gapSkill
- review-responseSkill
- scientific-runtimeSkill
- scientific-tool-onboardingSkill
- scrubSkill
- searchSkill
- setupSkill
- showSkill
- technical-reportSkill
- topicsSkill
- translateSkill
- workspaceSkill
- writing-polishSkill
The file
We split this scholaraio.mdc into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this Project Rule as the Cursor-native entry point.
- Distinctive: line 14
Read AGENTS.md at the repository root.
- Very specific: line 18
Use scholaraio --help and the specific skill instructions before running ScholarAIO CLI commands.
- Very specific: line 20
Write user-facing drafts, reports, exports, and analysis outputs under workspace/, not the repository root or scholaraio/.
- Very specific: line 22
Keep Cursor integration on native Project Rules plus the ScholarAIO CLI.
≈ “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: ScholarAIO project instructions and research workflow router alwaysApply: true --- # ScholarAIO Cursor Entry Use this Project Rule as the Cursor-native entry point. This rule was checked against Cursor's official rules documentation on 2026-04-10. Full shared project instructions live in `AGENTS.md`; do not duplicate them here. Before ScholarAIO work: - Read `AGENTS.md` at the repository root. - For deeper repo, runtime, or skill organization details, read `docs/guide/agent-reference.md`. - For paper search, reading, ingest, export, writing, or scientific-runtime tasks, read the matching workflow in `.claude/skills/*/SKILL.md`. - Use `scholaraio --help` and the specific skill instructions before running ScholarAIO CLI commands. - Write user-facing drafts, reports, exports, and analysis outputs under `workspace/`, not the repository root or `scholaraio/`. - Keep Cursor integration on native Project Rules plus the ScholarAIO CLI.
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.