agentleFS
Sign inStart free
theviderlabtheviderlab/tailored-cv/AGENTS.md

tailored-cv

AGENTS.md1 starsChanged 2 days agoMITView on GitHub

Context for AI coding agents (Claude Code, OpenCode and others) working in this repository. tailored-cv is a set of agent skills plus a small Node build. The skills tailor a CV and cover letter to a job posting from the user's professional profile, audit that profile for ATS, and debrief interviews. The build turns markdown into ATS-optimized PDFs with headless Chrome/Edge. Golden rule: never invent data. Everything in a CV or cover letter must come from the user's profile (workspace/profile/)…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 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 repository4 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run from cv/ (after npm install):

    line 35
  2. Very specific:

    Base files: Do not edit workspace/cv-base.md or workspace/cover-letter-base.md unless the user asks.

    line 48
  3. Very specific:

    Design: Keep the layout single-column and text-only (ATS).

    line 49
  4. Distinctive:

    Commits: Only when the user asks. The pre-commit hook (git config core.hooksPath .githooks) blocks personal data.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md

Context for AI coding agents (Claude Code, OpenCode and others) working in this repository.

What this project is

tailored-cv is a set of agent skills plus a small Node build. The skills tailor a CV and cover letter to a job posting from the user's professional profile, audit that profile for ATS, and debrief interviews. The build turns markdown into ATS-optimized PDFs with headless Chrome/Edge.

Golden rule: never invent data. Everything in a CV or cover letter must come from the user's profile (workspace/profile/) or from an explicit answer the user gave. When something is missing, ask.

Skills

The skills live in .claude/skills/<name>/SKILL.md. Read the matching file before acting:

The user wants to…Skill
Tailor a CV or cover letter to a posting, add facts to the profile, update an application statuscv-tailor
Review or improve the profile for ATS, without a postingprofile-audit
Record, transcribe, review or prepare for an interviewinterview

Layout

.claude/skills/      Skill instructions (markdown)
cv/                  Markdown → PDF build: build-cv.js, build-cover-letter.js, lib.js, design/, i18n.json
docs/                ATS guidelines (ats-guidelines.md) and README images
tools/               Interview recorder and transcriber (Python, run with uv)
examples/            Fictional demo workspace (Alex Morgan)
workspace.example/   Empty template for a user's workspace
workspace/           The user's private data (git-ignored; may be its own private repo)

Commands

Run from cv/ (after npm install):

npm run cv -- <path/to/cv.md>                      # CV PDF next to the md; fails above 2 pages
npm run cover -- <path/to/letter.md> [cv.md]       # cover letter PDF; fails if it overflows 1 page

Chrome/Edge is found automatically on Windows; elsewhere set CHROME_PATH.

Rules

  • Privacy. Personal data lives only in workspace/. Never copy it anywhere else, never commit it to this repo, and never send it to external services beyond the model itself. Use examples/alex-morgan/ for anything public.
  • Markdown contract. CV section headings are fixed English keys (see cv-tailor); do not translate or rename them. Translated PDF headings come from cv/i18n.json.
  • Base files. Do not edit workspace/cv-base.md or workspace/cover-letter-base.md unless the user asks. Each application gets its own folder in workspace/output/<company>-<role>/.
  • Design. Keep the layout single-column and text-only (ATS). Do not edit cv/design/*.css unless asked.
  • Language. Talk to the user in their language. The profile is in English; the CV follows the posting's language.
  • Commits. Only when the user asks. The pre-commit hook (git config core.hooksPath .githooks) blocks personal data; never bypass it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free