Skip to content
Back to search

vibe-resume-skill

AI 简历生成与排版 Skill|12 套可投递 HTML/PDF 模板。AI resume builder for creating, updating and tailoring resumes to any JD via Codex, Claude Code, Cursor & Trae.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kevinyoung-kw--vibe-resume-skill/badge.svg)](/listings/kevinyoung-kw--vibe-resume-skill)

HTML

<a href="/listings/kevinyoung-kw--vibe-resume-skill"><img src="/api/listings/kevinyoung-kw--vibe-resume-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 468 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: html-resume-builder
  3. description: Build one-page HTML/PDF resumes from copy-paste YAML using one of 12 official templates. HARD GATES: deliver exactly one A4 page; never invent a layout — copy assets/templates/<id> into output/<id>/ and edit that copy only. Keep a full inventory in raw.data.yaml. For each job, COPY selected entries into resume.data.yaml (polish there), then apply that file to a template. Apply pasted YAML by replacing visible text in the official resume.html, then run QA. Default template is basic-a4. Use when creating, iterating, polishing copy, migrating, exporting, or designing resume/CV HTML/PDF. For polishing resume copy, prefer writing-oriented models (Claude Fable 5 / Claude Opus 4.6-4.7 or Opus 5 / Kimi K3 / GLM-5.1-5.3-max / Qwen 3.8 Max); do not use GPT-5.6 Terra/Luna or GPT-5.5 Instant.
  4. ---
  5. # HTML Resume Builder
  6. Use this skill to produce polished, **one-page** resume artifacts from structured facts. The default loop is **data first**: keep a `raw.data.yaml` inventory, copy selected entries into one `resume.data.yaml` per job, then apply that file to an official template. The default output is an editable HTML file and an exported PDF that follows a selected template exactly enough for recruiting use: stable A4 dimensions, consistent typography, predictable spacing, clear hierarchy, verified screenshot, and no accidental sensitive-material leaks.
  7. This skill is intentionally workflow-heavy. Resume work fails when the model jumps straight into writing prose, invents a new HTML document, or nudges layout by eye without QA. Follow the **Mandatory Workflow** below before any other step.
  8. When expanding the template library, work one direction at a time: produce a brief, implement in an isolated workspace, QA and compare against the baseline, then seek user approval before admission. Do not split the resume into module Agents; components are AI-decided slots inside the selected template.
  9. ## Mandatory Workflow (do this every time)
  10. These steps are hard gates. Skipping them is a failed run, even if the page looks fine.
  11. There are two data files. Do not mix them.
  12. | File | What it is |
  13. |------|------------|
  14. | `raw.data.yaml` | 履历库. Every job, project, campus thing the user wants remembered. Can be long. **Never printed.** |
  15. | `resume.data.yaml` | One application. Copied from raw, then polished for this JD. This is what you apply to a template. |
  16. Job A and job B share the same raw. Each gets its own `resume.data.yaml` (e.g. `output/ai-intern/resume.data.yaml` vs `output/growth/resume.data.yaml`).
  17. ### 1. Collect facts into `raw.data.yaml`
  18. Extract education, internships, projects, skills, contacts, and assets into the inventory. Use `examples/raw.data.yaml` as the shape. Keep extra experiences even if they will not fit one page. Add `id` / `tags` on entries so later jobs can select them (`ai-product`, `growth`, `frontend`, …).
  19. **Show the raw file** so the user can copy it and keep adding facts. Do not hide the inventory in chat-only notes.
  20. Do **not** write `resume.data.yaml` yet unless the user already named a target job and asked to export.
  21. ### 2. For a job: copy from raw → `resume.data.yaml`
  22. When the user names a role or pastes a JD:
  23. 1. **Copy** (do not move) the matching entries from `raw.data.yaml` into a new `resume.data.yaml`. Set `layer: resume` and `source_raw`.
  24. 2. Leave unused entries in raw (frontend intern stays in raw when exporting an AI-product resume).
  25. 3. Polish **only** the copied `resume.data.yaml`: tighter summary/bullets, skill order, `target_role` / `jd`. Follow `references/copy-optimize.md`.
  26. 4. Show the selected id list + the resume YAML. Wait for accept.
  27. 5. Apply **that** `resume.data.yaml` to a template (step 3). Export is this copy logic, not a third published file.
  28. If they later say 投 B 岗位, start a new `resume.data.yaml` from the same raw. Do not overwrite job A's file.
  29. Never delete from raw to make one page. Cuts happen only on the resume copy.
  30. ### 2.5 Do not invent a polished sibling
  31. No `resume.polished.data.yaml`. The pair is raw (bank) vs resume (this job). 润色 writes into `resume.data.yaml`.
  32. ### 3. Copy the official template, then edit that copy only
  33. ```bash
  34. mkdir -p output
  35. cp -R assets/templates/<template-id> output/<template-id>/
  36. ```
  37. `python scripts/create_workspace.py --template <template-id> --output output/<template-id>` is equivalent.
  38. Edit **only** `output/<template-id>/resume.html` (and its local assets). Never edit files under `assets/templates/` for a candidate resume.
  39. ### 4. Forbidden
  40. - Writing a new HTML document from scratch, even if it "looks like" a template
  41. - Using a template that is not in the 12-id allowlist
  42. - Skipping QA
  43. - Switching templates mid-run unless the user asks
  44. - Introducing a mustache / Handlebars / template-engine rewrite of the 12 official files. There is no render engine. Apply YAML by replacing **visible text** in the official `resume.html` while keeping CSS, class names, semantic `data-*` markers (including `data-template="<id>"`), and structure
  45. ### 5. Template allowlist (12 ids)
  46. `basic-a4` (baseline) · `editorial` · `sidebar-compact` · `timeline-grid` · `minimal-prose` · `mono-raw` · `code-poetry` · `swiss-neue` · `bauhaus` · `corporate-classic` · `gov-red` · `folio-ledger`
  47. If the user does not pick a template, **default to `basic-a4` and say so**.
  48. ### 6. One page is a hard stop
  49. A resume is not deliverable unless it is exactly one A4 page.
  50. 1. Run existing QA scripts when they are present:
  51. - `python scripts/export_and_qa.py output/<id>/resume.html --pdf output/<id>/resume.pdf --template <id>`
  52. - `node scripts/check-template-id.mjs --html output/<id>/resume.html --template <id>`
  53. 2. If `pdfinfo` page count ≠ 1, **do not deliver**. Compress layout within the existing density / typography-floor rules, or ask the user (named cuts vs. keep-all vs. an explicit two-page exception).
  54. 3. If the user said `全部保留` / `不要删减`, do not delete facts to force one page — stop and ask.
  55. 4. A screenshot or HTML that looks "almost one page" is not enough. The PDF page count must be 1.
  56. `examples/demo/` is the out-of-the-box render: official `basic-a4` filled from `examples/demo.data.yaml`. Users can open `examples/demo/resume.html` immediately.
  57. ## When the AI may change the look(什么时候可以改模板)
  58. There are four different jobs. Do not mix them. “改模板” almost never means inventing HTML.
  59. ### A. 换数据(默认,随时可以,这不是改模板)
  60. User pastes YAML or says apply. Copy the official template, replace visible text, then tune density. Keep CSS, class names, `data-template`, and structure. This is the normal loop.
  61. ### B. 换官方模板(用户要「全变样」时,这是最好的改法)
  62. Same YAML, different allowlisted id. Always `cp -R` a fresh official folder. Never mix two templates' CSS.
  63. Do this when:
  64. - The user names a template (`swiss-neue`, `gov-red`, …)
  65. - The user says 换风格 / 全变样 / 太普通 / 换一套
  66. - The current template is a bad fit (e.g. `gov-red` for a geek role, `sidebar-compact` overflowing, `code-poetry` for a 国企投递)
  67. - The first deliverable used the default `basic-a4` and the user wants a restyle
  68. If unsure which official template fits, show the 12-id table and ask. Do not invent a 13th look.
  69. ### C. 在当前模板里微调版式(内容稳定之后才做)
  70. OK: font-size ±0.5–1pt, line-height, section/entry gaps, absolute coordinates, duplicating or deleting an existing official block of the same kind.
  71. Not OK: new sidebar, new grid, new color system, new font family, rewriting `resume.html` from scratch, stamping `data-template` onto invented markup.
  72. ### D. 发明新模板(正常写简历时禁止)
  73. Only follow `references/template-expansion.md`: one direction, brief first, isolated workspace, compare against `basic-a4`, user admits it. A color swap is not a new template. Do not edit `assets/templates/` during a candidate resume run.
  74. ## Core Principles
  75. - Treat a resume as both a **content artifact** and a **layout artifact**. Improve the wording, but keep the visual hierarchy and template constraints under control.
  76. - Prefer evidence-based statements. Write achievements as Situation/Task -> Action -> Result when space allows, and avoid fake metrics.
  77. - Preserve recruiter readability. Put internship work under `实习经历`, portfolio/project work under `项目作品/个人经历`, and skills under `核心能力`; do not move work into a misleading section just because it fits visually.
  78. - Preserve template fidelity before pursuing novelty. If a new template or variant is not at least as good as the baseline template in layout stability, visual rhythm, density, and recruiting readability, reject it instead of adding it to the template library.
  79. - For new templates, visual quality must be verified at full-page screenshot scale before admission.
  80. - Keep one-page resumes honest and visually full. If content is light, enlarge type, line-height, and section rhythm rather than padding with weak claims or leaving large blank areas. If content is dense, compress carefully without breaking hierarchy.
  81. - Let AI decide optional resume components inside the selected template's slots. Components such as campus experience, certificates, language ability, portfolio links, or tool chains may be added, renamed, merged, or omitted when they improve the resume, but they must not break the template structure or misclassify facts.
  82. - Never expose internal links, issue IDs, private group chats, patches, commits, document paths, raw prompts, or confidential tool names unless the user explicitly wants them shown.
  83. - Use a final QA pass. A resume is not done until PDF page count, fonts, text extraction, screenshot, spacing, and sensitive-word checks pass.
  84. ## Content Preservation & Deletion Gate
  85. Treat an existing resume and user-prepared resume copy as source material the user has already selected. **Do not silently delete or materially weaken it to make the page fit.**
  86. - Default to preservation mode when iterating an existing PDF, Word, PPTX, or HTML resume. Text the user pastes and explicitly asks to include also counts as selected resume content. Keep every company, role, project, date, metric, credential, named deliverable, link, and user-authored bullet unless the user approves its removal.
  87. - A major edit includes deleting an entire entry or bullet, merging entries so a distinct fact disappears, removing a metric/result, changing section ownership, or replacing a specific accomplishment with a generic summary. Ask before making any of these changes.
  88. - Compression is allowed without a separate approval only when it removes repetition or shortens syntax while preserving the same facts, ownership, result, and level of specificity.
  89. - If the requested content does not fit one page, first repair layout and wording within the readability limits below. If it still does not fit, **do not deliver**. Ask the user to choose: a denser but still readable one-page layout; a named list of lower-priority cuts; or an explicit two-page exception (never the default).
  90. - If the user says `全部保留`, `不要删减`, or equivalent, do not remove content. A one-page preference never overrides an explicit preservation request.
  91. - Maintain a short change ledger during iteration: `retained`, `compressed without fact loss`, and `proposed removal`. Show proposed removals to the user before applying them.
  92. ## Layout Hard Constraints
  93. These constraints override template defaults. They apply to every template in this family.
  94. ### Page Margins (页边距)
  95. - **Maximum page padding: 10mm on any side.** No template should have left/right/top padding exceeding 10mm. The A4 page is 210mm wide; content should occupy at least 190mm of horizontal space.
  96. - If a template uses absolute positioning, the leftmost content should start no later than 12mm from the page edge, and the rightmost content should end no earlier than 12mm from the right edge.
  97. - When the generated resume shows obvious blank strips on either side, reduce padding first before considering any other adjustment.
  98. - **Margins are also a floor, not just a ceiling.** Do not crush page padding below roughly 6mm to gain density. A resume whose content touches the paper edge reads as desperate, not efficient. Edges need quiet space to breathe.
  99. ### White Space Principle (留白原则)
  100. - The density rules above exist to prevent hollow, half-empty pages — they are **not** a mandate to stuff the page. Deliberate white space is part of good typography: page margins, breathing room between sections, and a calm bottom edge within the 15% budget are features, not defects.
  101. - Never manufacture density. Do not solve "the page has white space" by inventing extra components, splitting content into additional columns, breaking paragraphs into pill grids, or adding decorative filler blocks. A page filled with layout gimmicks is worse than a page with honest white space.
  102. - When content genuinely runs light, the correct tools are typography (slightly larger type, taller line-height, calmer section rhythm) and — only if the user has real material — one meaningful optional section. When in doubt, prefer a calm, slightly airy page over a crowded one.
  103. ### Density Adaptation (密度自适应)
  104. - Template HTML provides a **structural skeleton**. The font sizes, line-heights, and section gaps defined in templates are **reference values, not fixed**.
  105. - When filling a template with real content, AI must adapt spacing to fit the content volume:
  106. - **Content is light** (fewer experiences, shorter descriptions): increase font-size (+0.5–1pt), increase line-height (+0.05–0.1), increase section gaps slightly. The goal is a page that feels intentionally spacious and calm, not empty.
  107. - **Content is heavy** (many experiences, long descriptions): remove excessive section/entry gaps first, compress repeated wording without dropping facts, then keep font-size stable or reduce by 0.5pt max. Never go below 9pt for body text.
  108. - **Bottom whitespace > 15%**: this is a hard QA failure. Adjust font-size/line-height/section-gap upward until the page is visually balanced.
  109. - Do not leave large hollow areas. Do not pad with weak content to fill space — adjust typography instead.
  110. - Never shrink body text while large section or entry gaps remain. Small, thin text plus visible hollow bands is a layout failure even when the PDF is one page.
  111. ### Typography Readability Floor (正文字体下限)
  112. - Recruiter-facing body text must be at least `9pt` (`12px` in CSS) and normally use `font-weight: 400` or stronger. Weight `300` is reserved for dates, parentheses, captions, and other supporting labels, not paragraphs.
  113. - Body line-height should normally stay between `1.35` and `1.7`. Do not reduce line-height below the point where adjacent lines visually touch.
  114. - If the page is sparse, increase body size and line-height before increasing large inter-section gaps. If the page is dense, reduce gaps before reducing type.
  115. ### Avatar & QR (头像与二维码)
  116. - **Avatar must have zero border and zero border-radius.** No frames, no rounded corners, no shadows. A clean rectangular image, period.
  117. - Avatar must remain in its original color. Never apply grayscale, sepia, or any filter to a personal headshot.
  118. - QR codes may be grayscale if the template is monochrome, but must not be obscured or clipped by any other element.
  119. - If a QR code is present, it must be fully visible — no overlap with text, pills, or other components.
  120. ### Section Spacing (模块间距)
  121. - Section-to-section vertical gap should be proportional to the content density. Reference range: 4–7mm between major sections.
  122. - Within the same company or section, entry-to-entry gap: 2–3.5mm. Different companies may use 3–5mm, but should not look detached.
  123. - A blank vertical band larger than roughly two body line-heights between consecutive semantic blocks is a QA failure unless the selected template explicitly defines that area as an intentional visual zone.
  124. - These values flex based on content volume — they are not fixed. The goal is consistent visual rhythm across the full page, not mathematical equality.
  125. ## When Starting
  126. Run the Mandatory Workflow first. The steps below are intake details, not a license to skip YAML, the template copy, or QA.
  127. 1. Identify the target role and audience.
  128. - Examples: `AI 技术产品`, `AIGC 智能评测`, `AI 视觉内容编导`, `游戏视频设计`, `产品运营`.
  129. - If the user gives no role, infer from the strongest recent materials, then state the assumption.
  130. 2. Gather source materials.
  131. - Existing resumes: PDF, PPTX, DOCX, HTML.
  132. - Supporting materials: work summaries, project docs, portfolio websites, spreadsheets, screenshots.
  133. - Assets: avatar/headshot, QR code, portfolio URL, website URL.
  134. - Decide preservation mode: existing resume content and text explicitly requested for inclusion are `preserve by default`; background materials not marked for full inclusion may be selectively summarized only after the user understands that not every source detail will appear.
  135. 3. Choose the template from the 12-id allowlist only.
  136. - If the user does not name one, default to `basic-a4` and tell them you did.
  137. - Copy `assets/templates/<template-id>/` into `output/<template-id>/`. Do not write a new HTML file.
  138. - Future templates should live under `assets/templates/<template-name>/` only after admission.
  139. - If expanding the template library, follow `references/template-expansion.md` before implementing or accepting any new template.
  140. 4. Decide whether this is:
  141. - **Template migration**: style must match an existing resume.
  142. - **New resume from materials**: style comes from a bundled template.
  143. - **Iteration**: edit an existing HTML/PDF resume while preserving style.
  144. - **Template expansion**: propose one new style direction, implement in an isolated workspace, compare against the baseline, and seek user approval before admission.
  145. ## Recommended Workflow
  146. ### Step 1: Template Selection
  147. **先让用户选模板,再开始写内容。**
  148. 1. 向用户展示可用模板列表(名称 + 一句话风格描述),让用户指定:
  149. | 模板 | 风格 |
  150. |------|------|
  151. | basic-a4(默认) | 经典单栏,ATS 友好,适合所有场景 |
  152. | editorial | 双栏 Grid,字重层级分明 |
  153. | sidebar-compact | 深色侧栏,辨识度高 |
  154. | timeline-grid | 时间轴叙事,适合经历丰富 |
  155. | minimal-prose | Stripe 极简,留白即设计 |
  156. | corporate-classic | 外企极简,纯黑白,内容为王 |
  157. | gov-red | 党政风,庄重规范,适合国企/事业单位 |
  158. | folio-ledger | 年报档案索引,编号清晰,适合中高信息密度 |
  159. | mono-raw | Brutalist 风,工具即美学 |
  160. | code-poetry | 源代码隐喻,极客风 |
  161. | swiss-neue | 瑞士主义,隐形网格,克制优雅 |
  162. | bauhaus | 包豪斯几何,三原色点缀 |
  163. 2. 如果用户没有明确偏好,默认使用 **basic-a4**,并明确告诉用户。
  164. 3. 只允许上面这 12 个 id。用户点名 allowlist 之外的模板时,拒绝并列出允许的 id。
  165. 4. 用户确认后,锁定模板,不再中途切换(除非用户主动要求)。
  166. ### Step 1.5: Style Lock
  167. 模板确定后,检查并锁定视觉参数:
  168. - 页面尺寸:A4 竖版(除非用户另行要求)
  169. - 字体:通常为 PingFang SC
  170. - 色彩层级:主色、标题深灰、正文灰、辅助浅灰
  171. - 结构模块:姓名/信息、头像、个人介绍、教育经历、实习/工作经历、项目经历、核心能力、二维码
  172. - 组件位置:标题、分割线、日期对齐、正文缩进、头像和二维码位置
  173. 对于已有 HTML 模板,只编辑 `output/<template-id>/` 里的副本。除非模板已经无法修复,否则不要从零重建布局。
  174. ### Step 2: Fact Extraction into `raw.data.yaml`
  175. Extract facts from source files and websites into `raw.data.yaml` (schema: `schema/resume.schema.json`). **Show this inventory so the user can copy it and keep adding.** Only after a target job exists, copy selected entries into `resume.data.yaml`. Keep a short fact inventory before writing:
  176. - Education: school, major, dates, GPA/rank, awards/certificates.
  177. - Internships: company, role, dates, responsibilities, shipped outputs, measurable results.
  178. - Projects: name, context, actions, result, public evidence.
  179. - Skills: tools, workflows, domain knowledge, evaluation methods.
  180. - Links/assets: website, portfolio, QR, avatar/headshot.
  181. Rank facts by role relevance, but do not silently remove content from an existing resume. Mark lower-priority material as a proposed cut and ask the user before applying it. For a new resume built from raw supporting files, tell the user when the source volume requires representative selection rather than exhaustive inclusion.
  182. ### Step 3: Resume Copywriting
  183. If the user asked to 打磨内容 or match a JD, Mandatory Workflow **2.5** and `references/copy-optimize.md` come first. This step is the same writing bar used inside that YAML pass — it is not a substitute for showing a polished YAML file.
  184. 排版、改模板可用日常编程模型。**润色简历正文**用写作向模型。
  185. 推荐:
  186. - 海外:Claude Fable 5;Claude Opus 4.6 / 4.7(有 Opus 5 也行)
  187. - 国内:Kimi K3(K2.6 也偏写作);智谱 GLM-5.1 / 5.2 / 5.3-max;通义千问 Qwen 3.8 Max(结构化备选)
  188. 不要用:
  189. - GPT-5.6 Terra / Luna:同代里写作掉档最狠
  190. - GPT-5.5 默认 / Instant:日常默认档,文风空、套话多
  191. 其余模型不限定。
  192. Write in recruiter-friendly Chinese (or the user's language). Prefer compact STAR-style statements:
  193. - Situation/Task: the problem, scene, or requirement.
  194. - Action: what the candidate personally did.
  195. - Result: shipped output, measurable change, evaluation result, adoption, recognition, or public portfolio evidence.
  196. Good line pattern:
  197. `面对 [具体场景/问题],通过 [个人动作 + 方法/工具] 交付 [产物],结果 [已有事实]。`
  198. Avoid weak filler:
  199. - “具备较强能力”
  200. - “参与相关工作”
  201. - “负责部分事项”
  202. - “学习能力强”
  203. - “负责 / Helped with / Worked on” as the only verb
  204. If a metric is not public or not known, do not invent one and do not guess “约 30%”. Ask, then use verifiable alternatives: release status, review passed, coverage scope, samples/cases, team adoption, portfolio link.
  205. When a JD is present, weave only keywords the YAML already supports. Unproven JD skills stay in `optimize.notes` as ask / do-not-claim — never in `skills` or bullets.
  206. ### Step 4: Apply YAML into the official HTML (do not invent a layout)
  207. Use the selected template directory:
  208. - **Required:** `cp -R assets/templates/<template-id> output/<template-id>/` (or `scripts/create_workspace.py`). If iterating a user-provided HTML that already came from this skill, edit that copy.
  209. - Start from the official `resume.html`. Replace visible text so it matches the confirmed YAML. Keep CSS, class names, DOM structure, and `data-template="<id>"` / `data-resume-*` markers.
  210. - Add or remove entry blocks only by duplicating or deleting an existing official block of the same kind. Do not introduce a new grid, sidebar, or font system.
  211. - Replace only content and necessary asset references first. Adjust positions after content is stable.
  212. - Keep class names and style tokens consistent.
  213. - Forbidden: a blank `resume.html` written from scratch; any template id outside the allowlist.
  214. For a one-page A4 resume, use absolute-positioned blocks only when preserving a strict template. For new templates, stable CSS grids are acceptable, but always export and screenshot-test.
  215. ### Step 4.1: Component Slot DIY
  216. The selected template owns the structure; AI owns the component choice inside allowed slots.
  217. - Keep the default backbone unless the template contract says otherwise: header, intro, education, internship, project or personal experience, core abilities, footer/QR.
  218. - For a new resume assembled from raw materials, AI may add, rename, or merge optional sections when that improves the candidate's story. When iterating an existing resume, removing or merging a section requires the Content Preservation & Deletion Gate above.
  219. - AI should decide whether optional content deserves its own section or should be merged into education/core abilities/project experience.
  220. **Available section titles** (pick what fits the candidate; do not use all):
  221. | Category | Section titles |
  222. |----------|---------------|
  223. | Core (almost always present) | 个人介绍 · 教育经历 · 核心能力 |
  224. | Experience | 实习经历 · 工作经历 · 项目经历 · 个人项目 |
  225. | Campus / Student | 校园经历 · 社团经历 · 学生工作 · 志愿服务 |
  226. | Achievements | 竞赛经历 · 获奖情况 · 荣誉奖项 |
  227. | Skills & Certs | 专业技能 · 工具链 · 语言能力 · 证书/资格 |
  228. | Portfolio | 作品集 · 开源贡献 · 个人博客 |
  229. | Other | 兴趣爱好 · 自我评价 · 培训经历 · 科研经历 · 发表论文 |
  230. Naming rule: use the title that most honestly describes the content. 已正式入职的用「工作经历」,在校生用「实习经历」;有社团管理经验的单独列「社团经历」,没有就不硬凑。
  231. - Component DIY is not a reason to invent facts, add weak filler, or move internship work into project experience.
  232. - Do not spawn separate agents for individual resume components. Use subagents for template style research/implementation, then let the main resume-building pass fill components.
  233. ### Step 4.5: Density and White Space Tuning
  234. After the first PDF export, inspect the screenshot as a whole page, not only line by line. Apply the **Layout Hard Constraints** from above. Specific process:
  235. 1. **Check page margins first.** If left/right padding > 10mm, reduce it. This is the single most common cause of "looks too empty" feedback.
  236. 2. **Measure bottom whitespace.** If the last content element ends more than 15% above the page bottom, the page is too loose. Adjust in this order:
  237. - Increase body font-size by 0.5–1pt
  238. - Increase line-height by 0.05–0.1
  239. - Increase section gaps by 1–2mm
  240. - Only after all three are maxed out, consider adding an optional section (awards, tools, self-summary) — and only from real material the user provided. Never add extra columns, split rows, or decorative components purely to consume space; within the 15% bottom budget, remaining white space is intentional and acceptable
  241. 3. **If content is dense** and overflows or feels cramped:
  242. - Remove abnormal hollow bands and reduce section gaps first (down to 4mm minimum between sections)
  243. - Reduce entry gaps (down to 2mm minimum)
  244. - Compress repetition while preserving every fact
  245. - Reduce body font by at most 0.5pt, never below 9pt or regular weight
  246. - If it still does not fit, ask the user before deleting content or moving to two pages
  247. 4. **Never use `letter-spacing` for density control.** It is a design accent, not a spacing tool.
  248. 5. **Re-export and screenshot after each adjustment.** A page that passes CLI checks can still fail visually.
  249. ### Step 5: Asset Handling
  250. - **Avatar/headshot**: keep original color. No grayscale, no filters, no border, no border-radius, no shadow. Pure rectangular image with `object-fit: cover`.
  251. - **QR codes**: may be grayscale if the template is monochrome. Must not be clipped or overlapped by any element. Keep a quiet white margin around the scannable area.
  252. - **QR visibility**: if a QR code appears in the template, it must be 100% unobstructed. If layout pushes content over the QR, the QR must move or the content must shrink — never allow partial occlusion.
  253. - Website links: use blue underlined text when it should read as clickable.
  254. - If using demo assets, keep them fake and clearly non-personal.
  255. ### Step 6: Export and QA
  256. Run export and QA every time content or layout changes materially. **Skipping QA is forbidden.** If page count ≠ 1, the resume is not done — do not deliver it.
  257. ```bash
  258. python scripts/export_and_qa.py output/<id>/resume.html --pdf output/<id>/resume.pdf --template <id>
  259. node scripts/check-template-id.mjs --html output/<id>/resume.html --template <id>
  260. ```
  261. Minimum checks:
  262. 1. `pdfinfo` confirms `Pages: 1` and A4 portrait. This is a hard stop.
  263. 2. `pdffonts` confirms the intended font family, usually `PingFangSC-Regular` and `PingFangSC-Semibold`.
  264. 3. `pdftotext -layout` confirms module order and no old-person or old-template text remains.
  265. 4. Render a JPEG/PNG screenshot using `pdftoppm` and inspect visually.
  266. 5. Search for sensitive or stale terms:
  267. - old names, old emails, old phone numbers
  268. - `patch`, `commit`, `群聊`, `ones`, `内部链接` (ASCII terms match on word boundaries, so `dispatch`/`milestones`/`committed` do not false-positive)
  269. - unrelated self-media terms when the user asked to remove them
  270. 6. Check visual layout:
  271. - no overlap, clipping, text touching QR/avatar, or title/body collision
  272. - title-to-body spacing matches the section hierarchy
  273. - body line-height is not cramped
  274. - body text is at least 9pt/12px and recruiter-facing paragraphs are not rendered with light (`300`) weight
  275. - no unexplained vertical gap exceeds roughly two body line-heights between consecutive sections or entries
  276. - main content bottom whitespace is no more than 15% of page height; this is a hard QA gate, not a suggestion
  277. - no large hollow areas; light resumes should use slightly larger type and calmer spacing
  278. - section rhythm is consistent
  279. - QR and footer captions align
  280. 7. Check content preservation against the source inventory:
  281. - every original company, project, date, metric, credential, and user-authored bullet is retained or explicitly approved for removal
  282. - compressed wording preserves the original fact, ownership, specificity, and result
  283. - any pending deletion proposal is surfaced to the user instead of being applied silently
  284. When visual QA matters, show or inspect the rendered screenshot before declaring completion.
  285. ## Bundled Resources
  286. - `schema/resume.schema.json`: copy-paste resume data schema (name, title, target_role, contacts, summary, experience, projects, education, skills, plus optional `jd` / `optimize` that never print).
  287. - `examples/raw.data.yaml`: demo inventory (extra frontend / 社团 / 视觉 stay here).
  288. - `examples/demo.data.yaml`: one job export copied from that raw (AI 产品 intern).
  289. - `examples/demo/`: official `basic-a4` filled from `demo.data.yaml`.
  290. - `assets/templates/basic-a4/`: baseline one-page resume template. Single column, absolute positioning, blue-gray color scheme.
  291. - `assets/templates/editorial/`: dual-column grid. Left sidebar for education/skills/QR, right main for narrative. Monochrome (no color highlights), hierarchy through weight/size.
  292. - `assets/templates/sidebar-compact/`: dark sidebar (deep navy) + white main body. Avatar/contact/education/skills in sidebar, experience/projects in main. Tags for skills.
  293. - `assets/templates/timeline-grid/`: vertical timeline with dot nodes. Education in header meta, experiences along the spine, skill pills in footer.
  294. - `assets/templates/minimal-prose/`: ultra-clean single-column, Stripe/Notion docs aesthetic. No rules, no color — hierarchy purely through weight, size, and generous whitespace.
  295. - `assets/templates/mono-raw/`: Brutalist monospace (Menlo/SF Mono). Pure black-on-white, dashed dividers, `>` prefixed sub-headings, data in bold. Raw, honest, technical.
  296. - `assets/templates/code-poetry/`: source code metaphor. `/* name */` comment block, `// SECTION` headers, `fn title()` entries, orange-highlighted metrics, `import {}` skills. Left gutter with line numbers.
  297. - `assets/templates/swiss-neue/`: Swiss International Typographic Style. Invisible grid (16mm label column right-aligned), mathematical spacing (8/4.5/2.5mm), light-weight (300) muted-red name as sole accent. Zero decorative elements.
  298. - `assets/templates/bauhaus/`: geometric single-column layout with red, blue, and yellow accents for creative roles.
  299. - `assets/templates/corporate-classic/`: restrained black-gray corporate layout for formal delivery.
  300. - `assets/templates/gov-red/`: Song-type institutional layout with restrained red section rules.
  301. - `assets/templates/folio-ledger/`: European annual-report ledger with a full-height folio rail, numbered sections, and a single recruiter reading column.
  302. - `references/template-contract.md`: layout contract for the basic A4 template.
  303. - `references/template-expansion.md`: protocol for adding new template styles with template Agents and main-Agent acceptance gates.
  304. - `references/copy-optimize.md`: YAML-first content polish — STAR/tight verbs, JD keywords, no invented metrics, before/after pair.
  305. - `references/qa-checklist.md`: final QA checklist and common failure modes.
  306. - `scripts/create_workspace.py`: copy a template into a working directory (`output/<template-id>/`).
  307. - `scripts/export_and_qa.py`: export an HTML resume to PDF and run basic checks, including the `data-template` fingerprint and one-page gate.
  308. - `scripts/check-template-id.mjs`: fail if output HTML is missing `data-template="<id>"` from the allowlist.
  309. ## Quick Start Commands
  310. Prerequisites: Chrome or Chromium for PDF export, and poppler (`pdfinfo`/`pdffonts`/`pdftotext`/`pdftoppm`) for the QA checks. On macOS: `brew install poppler`. Missing poppler downgrades those checks to warnings instead of failing the run.
  311. Create a working copy from the bundled template:
  312. ```bash
  313. python scripts/create_workspace.py --template basic-a4 --output output/basic-a4
  314. ```
  315. Export and QA the resume (one-page + official-template fingerprint):
  316. ```bash
  317. python scripts/export_and_qa.py output/basic-a4/resume.html --pdf output/basic-a4/resume.pdf --template basic-a4 --strict-final
  318. node scripts/check-template-id.mjs --html output/basic-a4/resume.html --template basic-a4
  319. ```
  320. Use `--strict-final` for real candidate resumes so demo placeholders such as fake names, fake contact details, and `example.com` are rejected. The QA script also fails the resume when the main content bottom whitespace exceeds 15% of page height; use `--max-bottom-whitespace` only if a different template has an intentional footer system.
  321. ## Output Convention
  322. Default deliverables live under `output/<template-id>/`:
  323. - `output/<template-id>/resume.html` (official template copy, text replaced from YAML)
  324. - `output/<template-id>/resume.pdf` (exactly one A4 page)
  325. - `raw.data.yaml` at repo root or `output/raw.data.yaml` (inventory)
  326. - `output/<role-or-template>/resume.data.yaml` (this job, copied from raw)
  327. - Optional named exports: `<candidate-name>-<target-role>-模板版.html` / `.pdf`
  328. Final response should include:
  329. - Where the PDF and HTML are.
  330. - What sources were used.
  331. - What QA passed.
  332. - Any assumptions or missing assets.
  333. Keep the final response concise. If the user is still reviewing, summarize only the current change and the verification result.
README.md · README · 179 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ![Vibe Resume Skill:AI 简历生成与排版](assets/cover.png)
  2. # Vibe Resume Skill:AI 简历生成与排版
  3. **快速生成精美简历,快速更新和编排内容,把时间留给经历本身,而不是字号、间距和分页。**
  4. [![License](https://img.shields.io/badge/License-CC%20BY--NC%204.0-555555?style=flat-square)](LICENSE)
  5. [![HTML](https://img.shields.io/badge/Output-HTML%20%2B%20PDF-E34F26?style=flat-square)](assets/templates/basic-a4/resume.html)
  6. [![Skill](https://img.shields.io/badge/Format-Agent%20Skill-111111?style=flat-square)](SKILL.md)
  7. <p align="center">
  8. <a href="https://colaos.ai"><img src="assets/cola-logo.png" height="56" alt="Cola 支持"></a>
  9. &nbsp;&nbsp;
  10. <a href="https://workbuddy.homes/cases/submissions/vibe-resume/"><img src="assets/workbuddy-icon.svg" height="56" alt="WorkBuddy 蓝皮书"></a>
  11. </p>
  12. <p align="center">
  13. <sub>
  14. <a href="https://colaos.ai">Cola</a> 支持
  15. ·
  16. 收录于 <a href="https://workbuddy.homes/cases/submissions/vibe-resume/">WorkBuddy 蓝皮书</a>
  17. </sub>
  18. </p>
  19. `vibe-resume-skill` 是一套给 AI 编程助手使用的简历 Skill。把你的经历、现有简历或目标岗位交给它,就能生成一份排版完整的简历;后续新增经历、替换内容或调整投递方向,也可以直接通过对话完成。
  20. Skill 内置 12 套 A4 模板,并把一页排版、内容密度、头像、二维码和最终检查等要求写进了规则。你只需要说明想改什么,剩下的编辑与排版交给 AI。
  21. ![支持主流 Coding Agent](assets/demos/coding-agents.png)
  22. ## 适用场景
  23. 1. **从零整理一份新简历**
  24. 经历分散在项目文档、实习总结或作品集中,还没有形成完整简历。把材料和目标岗位交给 AI,它会先整理事实,再生成一页版本。
  25. `根据这些材料整理一份 AI 产品简历,先确认事实,再使用 basic-a4 输出 HTML 和 PDF。`
  26. 2. **更新一份已经排好的简历**
  27. 已经有满意的 PPT、PDF、Word 或 HTML 简历,但新增一段经历后,原来的分页、间距和对齐很容易被打乱。Skill 会尽量复用现有视觉语言,插入或替换内容,再重新平衡整页版式。
  28. `保留当前模板,把这段实习加入实习经历;不要删减其他内容,重新检查一页排版。`
  29. 3. **针对不同岗位维护多个版本**
  30. 同一段经历投递不同岗位时,事实不变,但顺序、标题、关键词和篇幅侧重需要调整。把 JD 一并提供,就可以生成对应版本。
  31. `基于这份 JD 调整为数据产品方向,保留原始事实,并单独导出一个版本。`
  32. 4. **只打磨内容,先不排版**
  33. 履历先堆在 `raw.data.yaml`。对着这份 JD 从 raw **复制**适合的经历,打磨成这一次的 `resume.data.yaml`,再套模板。投 B 岗用同一份 raw 再导一份,不要从 raw 里删。
  34. `从 raw.data.yaml 按这份 JD 导出 resume.data.yaml,先给我看选了哪些经历。`
  35. ![Vibe Resume Skill 工作原理](assets/demos/hero.png)
  36. ## 30 秒
  37. 1. 先往 [`examples/raw.data.yaml`](examples/raw.data.yaml) 里记履历;针对某个岗位再导出一份 [`examples/demo.data.yaml`](examples/demo.data.yaml) 这样的 `resume.data.yaml`。
  38. 2. 指定一套模板,例如 `swiss-neue`;不指定则默认 `basic-a4`。
  39. 3. 拿到一页 HTML/PDF。AI 必须套用官方模板,不能自己发明版式。
  40. 想先看成品:直接打开 [`examples/demo/resume.html`](examples/demo/resume.html)(这是 `basic-a4` 按 demo 数据渲染的结果)。
  41. ```text
  42. 把 examples/demo.data.yaml 套到 swiss-neue,输出一页简历。
  43. ```
  44. AI 什么时候可以改模板:
  45. - **换数据**:随时。复制 yaml,粘回来,只换字,不换版式。
  46. - **换官方模板**:要「全变样」时用这个。同一份数据套另一套(12 选 1),不要自己画。
  47. - **微调间距/字号**:内容填完、导出一看才动,而且只动现有模板。
  48. - **发明新模板**:正常写简历时不要。那是加模板库的流程,要单独同意。
  49. ## 怎么用
  50. 第一步,把仓库地址发给你的 AI 编程助手:
  51. ```text
  52. https://github.com/KevinYoung-Kw/vibe-resume-skill
  53. ```
  54. 第二步,让它安装 Skill:
  55. ```text
  56. 帮我安装这个 Skill,然后用它帮我写简历。
  57. ```
  58. 第三步,选择模板并提供材料。你可以上传已有简历,也可以直接发送一段经历。后续修改继续用自然语言说明即可:
  59. ```text
  60. 把这段实习加进去,保持原来的样式。
  61. 底部有些空,重新平衡一下排版。
  62. 针对这份 JD 调整为数据产品方向,再导出一版。
  63. ```
  64. 目前已在 Codex、Kimi Work、WorkBuddy 和扣子空间中实际测试。
  65. ## 12 套模板
  66. ![12 套真实 HTML 简历模板](assets/demos/templates.png)
  67. <details>
  68. <summary><b>展开查看全部 12 套模板</b></summary>
  69. <br>
  70. <h3>实用系</h3>
  71. <p>优先考虑招聘阅读顺序、信息密度与正式投递场景。</p>
  72. <table>
  73. <tr>
  74. <td align="center"><img src="assets/previews/basic-a4.jpg" width="160"><br><b>basic-a4</b><br><sub>经典单栏 · ATS 友好</sub></td>
  75. <td align="center"><img src="assets/previews/editorial.jpg" width="160"><br><b>editorial</b><br><sub>双栏 Grid · 字重层级</sub></td>
  76. <td align="center"><img src="assets/previews/sidebar-compact.jpg" width="160"><br><b>sidebar-compact</b><br><sub>深色侧栏 · 高辨识度</sub></td>
  77. <td align="center"><img src="assets/previews/timeline-grid.jpg" width="160"><br><b>timeline-grid</b><br><sub>时间轴 · 成长叙事</sub></td>
  78. </tr>
  79. <tr>
  80. <td align="center"><img src="assets/previews/minimal-prose.jpg" width="160"><br><b>minimal-prose</b><br><sub>克制单栏 · 留白舒展</sub></td>
  81. <td align="center"><img src="assets/previews/corporate-classic.jpg" width="160"><br><b>corporate-classic</b><br><sub>外企经典 · 内容优先</sub></td>
  82. <td align="center"><img src="assets/previews/gov-red.jpg" width="160"><br><b>gov-red</b><br><sub>党政风 · 庄重规范</sub></td>
  83. <td align="center"><img src="assets/previews/folio-ledger.jpg" width="160"><br><b>folio-ledger</b><br><sub>年报档案 · 编号索引</sub></td>
  84. </tr>
  85. </table>
  86. <h3>个性系</h3>
  87. <p>保留完整的设计语言,适合技术、设计与创意岗位。</p>
  88. <table>
  89. <tr>
  90. <td align="center"><img src="assets/previews/mono-raw.jpg" width="160"><br><b>mono-raw</b><br><sub>Brutalist · 等宽排版</sub></td>
  91. <td align="center"><img src="assets/previews/code-poetry.jpg" width="160"><br><b>code-poetry</b><br><sub>源代码隐喻 · 极客风</sub></td>
  92. <td align="center"><img src="assets/previews/swiss-neue.jpg" width="160"><br><b>swiss-neue</b><br><sub>瑞士主义 · 隐形网格</sub></td>
  93. <td align="center"><img src="assets/previews/bauhaus.jpg" width="160"><br><b>bauhaus</b><br><sub>包豪斯几何 · 三原色点缀</sub></td>
  94. </tr>
  95. </table>
  96. </details>
  97. 模板不是简单换色。每套模板都有独立的信息结构、字号层级、间距节奏与适用场景。
  98. ## AI 会自动处理什么
  99. - 根据经历和目标岗位整理内容,保留真实事实,不编造指标
  100. - 需要时先打磨 YAML(紧句、强动词、JD 关键词),给出 before/after,再套官方模板
  101. - 区分教育、实习、项目与能力,避免经历放错位置
  102. - 根据内容多少调整字号、行距与段落间距
  103. - 尽量保持一页,并避免文字溢出、重叠或异常换行
  104. - 保持头像原色,确保二维码清晰且不被遮挡
  105. - 导出后检查整页效果,发现问题继续修改
  106. ## Star History
  107. <a href="https://www.star-history.com/?repos=KevinYoung-Kw%2Fvibe-resume-skill&type=date&legend=top-left">
  108. <picture>
  109. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=KevinYoung-Kw/vibe-resume-skill&type=date&theme=dark&legend=top-left&sealed_token=MGIwE7UOti3rlRQhmUe4-jfNj-wVj54h-tryO1DkXRbrtetNAtNq5028PtHQLc7VgTAMh8tTS_urWW5CDoxb7o7xEiKrKO0DFtbynQNZmqlwWU5ySWUKGeZjSn2JemO-5cIcYE1TthUw0ReUs-L75kyg7TNNdHXZI-9nTDPtBuVebQCK9EGsPcXiED8O" />
  110. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=KevinYoung-Kw/vibe-resume-skill&type=date&legend=top-left&sealed_token=MGIwE7UOti3rlRQhmUe4-jfNj-wVj54h-tryO1DkXRbrtetNAtNq5028PtHQLc7VgTAMh8tTS_urWW5CDoxb7o7xEiKrKO0DFtbynQNZmqlwWU5ySWUKGeZjSn2JemO-5cIcYE1TthUw0ReUs-L75kyg7TNNdHXZI-9nTDPtBuVebQCK9EGsPcXiED8O" />
  111. <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=KevinYoung-Kw/vibe-resume-skill&type=date&legend=top-left&sealed_token=MGIwE7UOti3rlRQhmUe4-jfNj-wVj54h-tryO1DkXRbrtetNAtNq5028PtHQLc7VgTAMh8tTS_urWW5CDoxb7o7xEiKrKO0DFtbynQNZmqlwWU5ySWUKGeZjSn2JemO-5cIcYE1TthUw0ReUs-L75kyg7TNNdHXZI-9nTDPtBuVebQCK9EGsPcXiED8O" />
  112. </picture>
  113. </a>
  114. ## Contributing
  115. 欢迎提交 Issue、文档修正和模板建议。新模板需要经过完整预览与质量检查后才会加入。
  116. ## License
  117. [CC BY-NC 4.0](LICENSE)。个人与非商业用途可按许可证使用;商业使用请联系作者。
  118. ---
  119. <p align="center">
  120. <img src="assets/wechat-qr.jpg" width="220" alt="公众号:水的实践说"><br>
  121. <sub>关注公众号「水的实践说」获取更多 AI 实践内容</sub>
  122. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.