job-hunt-kit
CLAUDE.md2 starsChanged 3 months agoMITView on GitHub
@AGENTS.md @docs/operating/systems.md AGENTS.md is the cross-agent filename (Linux Foundation stewardship, ~60k repos) — a filename agreement and nothing more: no schema, no sections, just "this is where the instructions are". Most other agents read it natively. Claude Code does not, whatever a handful of secondary sources claim, so the @AGENTS.md line above is load-bearing rather than decorative: delete it and Claude Code gets a one-word instruction file. Do not write instructions here. Two copies drift, and the one that drifts…
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apply-formSkill
- cover-letterSkill
- evaluate-roleSkill
- job-triageSkill
- publishSkill
- research-companySkill
- setupSkill
- sync-appliedSkill
- tailor-cv-batchSkill
- tailor-cvSkill
The file
We split this CLAUDE.md 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 15
Do not write instructions here.
≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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
jobs-db
@AGENTS.md @docs/operating/systems.md
<!--
This file is a stub on purpose. `AGENTS.md` is the source of truth and everything is written there.
`AGENTS.md` is the cross-agent filename (Linux Foundation stewardship, ~60k repos) — a filename
agreement and nothing more: no schema, no sections, just "this is where the instructions are". Most
other agents read it natively. **Claude Code does not**, whatever a handful of secondary sources
claim, so the `@AGENTS.md` line above is load-bearing rather than decorative: delete it and Claude
Code gets a one-word instruction file.
Do not write instructions here. Two copies drift, and the one that drifts is the one nobody is
reading at the time. `core/test_portable_workflows.py` fails if this file grows prose of its own.
-->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.

