Tailoring a CV

The tailoring pipeline is a Claude Code skill, not a build script — the interesting parts are conversations, and two of them are approvals.

/sumisura:tailor-cv

Three ways to start

Input	What happens
A job description (pasted text or a URL)	Selection and Rewrite target that job; a cover letter is drafted too
A tracked Application (“the Acme backend role”)	Same, using the Job Description already saved, and the Generation is recorded back against that Application
Nothing (Default Mode)	A general-purpose CV from your strongest material — no cover letter

The pipeline

1. Selection — which Entries belong on this one page.
2. Rewrite — bullets re-worded toward the job’s language. Plus a cover letter draft when there is a job, drawn from your Cover Letter Snippets if you have any.
3. Groundedness check — every rewritten bullet compared against its source.
4. Text Review — you approve. CV and cover letter are approved independently. Nothing renders before this.
5. Render — Typst produces the PDFs.
6. PDF checks — page count, ATS-parsability of the text layer, and the document language.
7. Visual Review — you approve the rendered result.

Checks are advisory by design: exit 0 clean, 1 flagged, 2 could not run. They inform a checkpoint where you are already looking; they never block or silently edit.

Where the files go

Every run gets its own directory, so a later run never overwrites an earlier one:

output/<label>-<UTC yyyymmdd-hhmmss>/
├── cv.pdf
├── cover-letter.pdf
├── data.json          # what the template rendered
└── selection.json     # Entries chosen + every source→rewrite pair

selection.json is what lets a groundedness verdict be re-derived later. output/ is gitignored and safe to delete; Application records survive and show a “no longer on disk” note.

Running a check by hand

./plugins/sumisura/skills/tailor-cv/scripts/quality-check.sh \
  groundedness --selection output/<slug>/selection.json

./plugins/sumisura/skills/tailor-cv/scripts/quality-check.sh \
  pdf --pdf output/<slug>/cv.pdf --data output/<slug>/data.json

Both wrap backend/cmd/cvcheck, the same Go code the web app calls. Add --json for machine-readable output. No running backend is needed.

Rendering manually

typst compile --root . template/cv.typ output/<slug>/cv.pdf \
  --input data=output/<slug>/data.json

The templates are pure presentation: they read one JSON file and lay it out. Changing your CV’s look means editing template/cv.typ, not the pipeline.