mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-09-17 00:26:26 +00:00
docs(cv): flag hardcoded English section headings for non-English CVs (#200)
The moderncv template's section headings (Core Competencies, Professional Experience, Education, Languages, Publications, Honors and Awards, References) and the References boilerplate line are literal English text the workflow never translates, so a CV localized in prose can sit under English scaffolding. Adds an illustrative, fork-aware rule to 05-cv-templates.md (translate the headings too, whatever your template defines) plus a verification-checklist item in CLAUDE.md. Ties into the CV-language profile setting from #179. By @Lautaro073. Heading list corrected against the stock template on review (Publications/Honors and Awards in, non-existent Independent Projects out; made illustrative for forks).
This commit is contained in:
@@ -1,5 +1,5 @@
|
|||||||
---
|
---
|
||||||
framework_version: 1.2.0
|
framework_version: 1.2.1
|
||||||
---
|
---
|
||||||
|
|
||||||
# CV Templates and Tailoring Guide
|
# CV Templates and Tailoring Guide
|
||||||
@@ -100,6 +100,10 @@ Two related patterns are fine and should be kept:
|
|||||||
- `\vspace{1pt}` immediately after `\section{...}` (between section heading and first item) - this is between the heading and the list, not between list items.
|
- `\vspace{1pt}` immediately after `\section{...}` (between section heading and first item) - this is between the heading and the list, not between list items.
|
||||||
- `\vspace{3pt}` between top-level `\cventry` blocks in Professional Experience or Education - this gives breathing room between roles and renders consistently.
|
- `\vspace{3pt}` between top-level `\cventry` blocks in Professional Experience or Education - this gives breathing room between roles and renders consistently.
|
||||||
|
|
||||||
|
### Section headings must match the CV's language (important)
|
||||||
|
|
||||||
|
Section headings such as `\section{Core Competencies}`, `Professional Experience`, `Education`, `Languages`, `Publications`, `Honors and Awards`, `References` (and any others your template defines), plus the `Available upon request.` line under References, are all **literal English text baked into the template** - they do not translate themselves. Whenever the CV language (see `CV language` in the candidate profile) is not English, translate every one of these too, whatever they are, not just the body prose - a CV with a fully localized profile statement and bullets sitting under untouched English section headers reads as sloppy and inconsistent, and it's an easy thing to forget precisely because the prose translation is the obvious, visible part of the job. Worked example for Spanish: `Competencias Clave`, `Experiencia Profesional`, `Educaci\'on`, `Idiomas`, `Publicaciones`, `Distinciones y Premios`, `Referencias`, `Disponibles a solicitud.` The same rule applies for any other target language - check this explicitly during the verification pass.
|
||||||
|
|
||||||
## Section-by-Section Tailoring
|
## Section-by-Section Tailoring
|
||||||
|
|
||||||
### Profile Statement / Elevator Pitch (Best Practice)
|
### Profile Statement / Elevator Pitch (Best Practice)
|
||||||
|
|||||||
@@ -120,6 +120,7 @@ After creating or updating a CV or cover letter, re-read the generated file and
|
|||||||
- [ ] Agentic coding / AI tooling references mention **Claude Code** by name
|
- [ ] Agentic coding / AI tooling references mention **Claude Code** by name
|
||||||
- [ ] Cover letter is addressed to the correct person (or "Dear Hiring Manager" if unknown)
|
- [ ] Cover letter is addressed to the correct person (or "Dear Hiring Manager" if unknown)
|
||||||
- [ ] Cover letter fits approximately one page
|
- [ ] Cover letter fits approximately one page
|
||||||
|
- [ ] CV section headings (`\section{...}`) and the References boilerplate line match the CV's language, not left as the English template defaults (see `05-cv-templates.md`)
|
||||||
|
|
||||||
### Compiled PDF verification (MANDATORY - never skip)
|
### Compiled PDF verification (MANDATORY - never skip)
|
||||||
Both documents MUST be compiled and visually inspected via the Read tool on the PDF output. "Looks fine in the .tex" is not acceptable - LaTeX page-break decisions are unpredictable. Iterate until these all pass:
|
Both documents MUST be compiled and visually inspected via the Read tool on the PDF output. "Looks fine in the .tex" is not acceptable - LaTeX page-break decisions are unpredictable. Iterate until these all pass:
|
||||||
|
|||||||
Reference in New Issue
Block a user