dl-research-workflow
CLAUDE.md4 starsChanged 39 days agoMITView on GitHub
Read AGENTS.md, AI_START.md and docs/00_start.md before project work. The same scientific contracts and authorization boundaries apply across assistants. Canonical skills are in .agents/skills/. Projects initialized with --agent claude also contain .claude/skills/ copies for native discovery. These copies must match their canonical counterparts; do not edit both independently. If a skill is unavailable to native discovery, read its canonical SKILL.md explicitly. Tool integrations and scheduling must be verified in the current host. Do not install global packages or modify account/configuration settings…
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- academic-humanizerSkill
- citation-verificationSkill
- claim-numerics-auditSkill
- cover-letterSkill
- experiment-planSkill
- experiment-runnerSkill
- journal-scoutSkill
- paper-auditSkill
- paper-illustrationSkill
- paper-planSkill
- paper-writeSkill
- research-data-auditSkill
- research-ideationSkill
- research-publicationSkill
- research-quality-gateSkill
- research-refineSkill
- result-to-claimSkill
- scientific-figure-makingSkill
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 3
Read AGENTS.md, AI_START.md and docs/00_start.md before project work.
- Very specific: line 10
If a skill is unavailable to native discovery, read its canonical SKILL.md explicitly.
- Distinctive: line 12
Do not install global packages or modify account/configuration settings on startup.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Research project entry point
Read AGENTS.md, AI_START.md and docs/00_start.md before project work.
The same scientific contracts and authorization boundaries apply across assistants.
Canonical skills are in .agents/skills/. Projects initialized with --agent claude
also contain .claude/skills/ copies for native discovery. These copies must match
their canonical counterparts; do not edit both independently.
If a skill is unavailable to native discovery, read its canonical SKILL.md
explicitly. Tool integrations and scheduling must be verified in the current host.
Do not install global packages or modify account/configuration settings on startup.
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.