# Resume Builder

> Use when a resume must be written into the user's own Word template: "이력서 만들어줘", "이력서 docx", "Word 템플릿에 이력서", "resume docx", "build my resume from this template". Catalog, build, check, PDF, fit.

- Skill: `newkayak12/resume-builder` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx get-skill add newkayak12/resume-builder`
- Raw SKILL.md: https://api.skillmd.com/api/skills/newkayak12/resume-builder/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: newkayak12 (https://skillmd.com/u/newkayak12)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/newkayak12/resume-builder

---


# Resume Builder — resume-deck.mdx into the user's own .docx

The user's template is the toolchain; the build copies its look, never a re-styled copy. **Not for** what
the resume says (`manage` step 9 designs `resume-skeleton.md`) or a pptx (`deck-builder`).

Engine, run from the workspace root: `python3 ${CLAUDE_PLUGIN_ROOT}/skills/resume-builder/scripts/resume.py <cmd>`
(`catalog`, `build`, `render`; one JSON object each). Detail: `references/resume.md`.

## Process

1. **Catalog.** `catalog --template template/<file>.docx`: paragraph styles (id, name, count, sample,
   suggested role) and `looks` (each distinct size, weight, colour, list once, with its text).
2. **Front matter.** In `resume-deck.mdx`: `template:`, `pages:` (the user's budget), and one mapping.
   `styles:` role → paragraph style when the template has real styles; `samples:` role → the opening
   text of the template paragraph whose look it takes when every line is `Normal`.
   Roles: `#` name, `##` section, `###` entry, `-` bullet, plain body; any other `{role} text`.
3. **Build.** `build` copies the template, drops its sample body, writes each line in its role's look
   (numbering included), keeps the photo on the first paragraph. A role mapped nowhere, a style the
   template lacks, or a sample text no paragraph starts with is refused before anything is written.
4. **Final checks.** The build output carries `warnings` (an unconfirmed `[확인 필요: …]` line is kept
   and named) and `ai_traces: {removed, reported}`: an AI disclaimer left in alt text ("AI-generated
   content may be incorrect") is removed; an AI tool named in the document properties or an AI phrase
   in the visible text is reported and never deleted. Say each `reported` item to the user.
   Nothing is called submittable before `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/office_render.py final-check
   [--dir build] [--allow "Claude Code,Codex"] [--author NAME]` has run over `resume.docx` and `resume.pdf`:
   one verdict per file (`깨끗함` or the list), exit non-zero on any finding. It checks alt-text
   disclaimers (removed), document properties naming an AI tool or a library (`--author` rewrites
   creator and last editor in the docx), and text, notes and PDF metadata for AI phrases and work
   annotations (`[확인 필요`, `TODO`, `FIXME`, `(본인 확인`, `Generated with`, `Co-Authored-By`, a model as
   writer). Findings are reported, never deleted. `--allow` lists the tools the person really lists as
   their own skills. Say every finding; the person decides.
5. **Render.** Only when the user says: `render` writes `build/resume.pdf`, counts pages against `pages:`,
   rewrites the page previews `build/pages/resume-p-N.png` (stale ones deleted) and prints the
   `final_check` verdicts.
6. **Review.** After every render, not only when over budget, run `render-review` on the PDF and its fresh previews.
7. **Fit.** Over budget: `over_lines` is the number of text lines past the last allowed page. Propose
   cuts with their line counts (a section, a block to one bullet) and wait. Cut text, never type size,
   line spacing or margins. Then render and review again.

The user's material never goes to git: the engine refuses a template, source or output a git repository
would carry (`.gitignore` it or work outside it).

## Output Template

```
이력서 <빌드함 | 안 함> — <paragraphs>줄, 템플릿 <file>
매핑: <styles | samples>로 <roles>
최종 검사: final-check <파일별 깨끗함 | n건 (<항목>)> · AI 흔적 <removed>건 제거 · [확인 필요] <n>건
렌더: <pages>쪽 / 예산 <pages>쪽 · 넘친 줄 <over_lines | 없음 | 렌더 안 함>
정하실 것: <잘라낼 후보와 줄 수 | 없음>
```

## What Claude Does / What You Do

| Claude | You |
|---|---|
| Lists the template's styles and looks, proposes the role mapping | Confirm the mapping; say which lines are which when the template does not |
| Builds into your template, keeps the photo, runs the final AI-trace check | Provide the template and `resume-deck.mdx`; keep both out of git |
| Reports every unconfirmed line and every reported AI trace | Answer `[확인 필요]` lines; decide what to do with a reported phrase |
| Renders when told, sizes the cut by `over_lines`, waits | Say when to render; choose what to cut |

## Related Skills

- `manage` — step 9 designs the resume (`resume-skeleton.md`) and calls this skill to build it
- `render-review` — page-by-page review of the rendered PDF
- `deck-builder` — the pptx counterpart; same renderer and the same final AI-trace check
- `write:like-me` — the voice of every sentence written into the source

