render-resumelisted

Compile a LaTeX resume to PDF with latexmk (falling back to tectonic or pdflatex) and report the output path, surfacing compile errors clearly. Use whenever the user wants to build, render, compile, or generate the PDF of their resume .tex — typically right after tailoring, or to rebuild the master. Detects the available TeX engine and gives install guidance if none is present.
DhruvPrajapati4/apply-kit · ★ 0 · AI & Automation · score 70

Install: claude install-skill DhruvPrajapati4/apply-kit

# render-resume Compile a resume `.tex` (default: the scratchpad `tailored.tex`) to PDF. Deterministic — no tailoring decisions happen here. ## Input - Path to a `.tex` (default: `tailored.tex` in the scratchpad; falls back to the working master, `master.tex` in the scratchpad or `./resume/main.tex`, if asked to render the master). ## Engine fidelity — important This resume is authored for **pdfLaTeX** (`\pdfgentounicode` for ATS + `roboto` Type1 fonts). `latexmk` (→ pdflatex) renders it **faithfully** and needs no shim — prefer it. **Tectonic runs XeTeX and does NOT render this resume correctly:** it crashes on `fontawesome5`, lacks the pdfTeX ATS primitives, and falls back from Roboto to a Computer Modern serif. `render.sh` auto-shims tectonic so it at least produces a PDF, but treat that as a rough preview only — the final PDF the user submits should come from pdflatex/latexmk (or Overleaf). Tell the user this if only tectonic is available. ## The page budget apply-kit does not force a one-page resume. The budget is the **master resume's own page count**, so a two- or three-page senior/staff/manager master stays that long and a one-page master stays one page. A tailored copy may come in shorter than the budget; it may never come in longer. Before rendering a tailored resume, read the budget from the `.page-budget` file next to the source master (written by `ingest-resume`) and pass it as the script's second argument. If that file does not exist, ask the user how m