make-resume
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/make-resume：制作可编辑简历
/make-resume: Create Editable Resume
生成真正可编辑的中文 HTML 简历，而不是把简历截图嵌入页面。用户可以在浏览器中继续修改文字、照片、字体、颜色和加粗内容，并通过打印导出 PDF。
Generate truly editable Chinese HTML resumes, instead of embedding resume screenshots into the page. Users can continue to modify text, photos, fonts, colors, and bold content in the browser, and export PDF via printing.
资源定位
Resource Location
ASu 资源支持两种布局，按以下顺序定位：
- Claude Code 安装布局：；
../../assets/asu/ - 仓库插件布局：。
../../assets/
只有候选目录同时包含 、、，以及 三部件（ / / ）与 下全部 18 个壳文件时才使用它，避免把其他 skill 的同名目录或不完整安装误判为 ASu 资源：
resume-data-template.jsontemplate-overview.jpgfictional-resume-photo.pngtemplates-html/frame/base.csstoolbar.htmleditor.jstemplates-html/- ：匿名简历内容结构；
resume-data-template.json - ：18 套模板共享的外框（样式 / 顶部工具栏 / 编辑脚本）单一来源；
templates-html/frame/ - ：18 个中文模板壳文件（纯设计稿，无工具栏与脚本；交付前需经 scripts/inline-template.mjs 内联为自包含 HTML）；
templates-html/ - ：模板预览图；
template-overview.jpg - ：虚构示例照片，只用于模板演示。
fictional-resume-photo.png
如果 skill 被单独复制到其他目录，先从当前 skill 目录向上依次定位 与 ，不要凭空创建模板资源。
assets/asu/assets/如果向上查找后两种布局都找不到完整资源，必须显式说明“模板资源未随 skill 一起安装”，并启用后备方案：
- 优先创建简洁 A4 可编辑 HTML，保留浏览器编辑、打印隐藏工具栏和 PDF 导出能力；
- 不承诺 18 套模板、模板预览图、示例照片或原模板复刻精度；
- 交付说明中写明当前使用的是后备模板，以及限制：视觉风格较少、不能保证与仓库模板完全一致；
- 不因为资源缺失而静默降级，也不把缺失资源重新伪造为“已使用官方模板”。
ASu resources support two layouts, located in the following order:
- Claude Code Installation Layout: ;
../../assets/asu/ - Repository Plugin Layout: .
../../assets/
Only use the candidate directory if it contains all of the following items at the same time, to avoid misjudging directories with the same name from other skills or incomplete installations as ASu resources:
- : Anonymous resume content structure;
resume-data-template.json - : Single source of shared outer frames (styles / top toolbar / editing scripts) for 18 sets of templates;
templates-html/frame/ - : 18 Chinese template shell files (pure design drafts without toolbars or scripts; must be inlined into self-contained HTML via scripts/inline-template.mjs before delivery);
templates-html/ - : Template preview image;
template-overview.jpg - : Fictional sample photo, only used for template demonstration.
fictional-resume-photo.png
If the skill is copied separately to another directory, first locate and by moving up from the current skill directory in sequence, do not create template resources out of thin air.
assets/asu/assets/If neither layout can be found with complete resources after searching upwards, you must explicitly state "Template resources are not installed with the skill" and enable the fallback solution:
- Prioritize creating a concise A4 editable HTML, retaining browser editing, print-hidden toolbar and PDF export capabilities;
- Do not promise 18 sets of templates, template preview images, sample photos or the replication accuracy of the original templates;
- Clearly state in the delivery instructions that the fallback template is currently in use, along with limitations: fewer visual styles, cannot guarantee full consistency with repository templates;
- Do not silently degrade due to missing resources, nor forge missing resources as "official templates used".
工作流程
Workflow
- 先按“输入清单”盘点材料；用户提供主张—证据账本时，按 账本状态规则 读取事实。缺少关键字段时按“缺失字段补问规则”补问，无法补齐时使用 或
待补充占位，不捏造经历。待确认 - 如果用户上传 PDF、已有简历、截图、图片或文档，先提取内容并检查布局；截图类输入还要分析栏位、间距、字体层级、颜色、照片位置和分页，再重建为 HTML。
- 按“模板选择矩阵”选择模板、页数和风格；内容能在正常字号下形成完整单页时优先单页，不因模板预设第二张页面而扩页。如果资源缺失，启用后备模板并说明限制。
- 输出 HTML 文件，保持文字和布局可编辑；工具栏放在页面外并在打印时隐藏。内置模板以壳文件形式存放（纯设计稿，无工具栏/脚本），交付给用户前必须经 内联成自包含 HTML（含样式、顶部工具栏、编辑脚本），不能直接把壳文件当交付物。
scripts/inline-template.mjs - 把 print-preview 作为导出前强制 QA：打开或模拟打印预览，检查分页、双栏、照片比例、长文本溢出、中文字体、打印边距和 A4 纸张效果；再按 A4 页面平衡与视觉密度 QA 测量每页内容占用并保存整页截图。发现问题先修复 HTML/CSS 再交付。
- 用户需要 PDF 时，按“PDF 导出验收标准”说明浏览器打印设置或导出命令，或按用户要求生成 PDF；不要用截图替代可编辑源文件。
正式成稿只使用账本中适用于当前岗位且状态为“已确认”的主张；“待确认”只可保留在内部草稿中，导出最终 PDF 前必须确认或删除。“已过期”和“不采用”的主张不得进入对外材料。
- First inventory materials according to the "Input Checklist"; when the user provides a claim-evidence ledger, read facts according to the Ledger Status Rules. When key fields are missing, follow the "Missing Field Follow-up Rules" to ask supplementary questions; if unable to complete, use or
To be supplementedas placeholders, do not fabricate experiences.To be confirmed - If the user uploads PDFs, existing resumes, screenshots, images or documents, first extract the content and check the layout; for screenshot inputs, also analyze fields, spacing, font hierarchy, colors, photo positions and pagination, then reconstruct into HTML.
- Select templates, page count and style according to the "Template Selection Matrix"; prioritize single-page when content can form a complete single page at normal font size, do not expand pages due to the template's preset second page. If resources are missing, enable the fallback template and explain the limitations.
- Output HTML files, keeping text and layout editable; place the toolbar outside the page and hide it during printing. Built-in templates are stored as shell files (pure design drafts without toolbars/scripts), must be inlined into self-contained HTML (including styles, top toolbar, editing scripts) via before delivery to users, cannot directly use shell files as deliverables.
scripts/inline-template.mjs - Use print-preview as mandatory QA before export: Open or simulate print preview, check pagination, two-column layout, photo ratio, long text overflow, Chinese fonts, print margins and A4 paper effect; then measure the content occupancy of each page and save full-page screenshots according to A4 Page Balance and Visual Density QA. Fix HTML/CSS first before delivery if problems are found.
- When the user needs a PDF, explain browser print settings or export commands according to the "PDF Export Acceptance Criteria", or generate a PDF as required by the user; do not use screenshots instead of editable source files.
Only use claims in the ledger that are applicable to the current position and marked as "Confirmed" for the final draft; "To be confirmed" can only be retained in internal drafts, must be confirmed or deleted before exporting the final PDF. Claims marked as "Expired" and "Not adopted" must not be included in external materials.
输入清单
Input Checklist
先从用户消息、附件和项目文件里抽取已有信息，再只补问真正影响交付的缺口。
- 基础信息：姓名、电话、邮箱、城市/籍贯、求职方向、个人主页/GitHub/作品集（可选）；
- 教育背景：学校、学历、专业、起止时间、GPA/排名、主修课程、奖项；
- 实习/工作：公司或团队、岗位、起止时间、业务背景、个人职责、技术栈、结果证据；
- 项目经历：项目名称、目标岗位相关性、个人边界、技术栈、核心动作、结果证据、可展示链接或截图；
- 技能：语言、框架、数据库、中间件、工具链、英语/证书；
- 投递目标：岗位名称、JD、校招/社招、页数要求、风格偏好、是否需要照片；
- 输出要求：HTML 保存位置、是否同时导出 PDF、文件命名和隐私处理。
First extract existing information from user messages, attachments and project files, then only ask supplementary questions for gaps that truly affect delivery.
- Basic Information: Name, phone number, email, city/hometown, job-seeking direction, personal homepage/GitHub/portfolio (optional);
- Educational Background: School, degree, major, start/end time, GPA/ranking, major courses, awards;
- Internship/Work Experience: Company or team, position, start/end time, business background, personal responsibilities, tech stack, result evidence;
- Project Experience: Project name, relevance to target position, personal scope, tech stack, core actions, result evidence, displayable links or screenshots;
- Skills: Languages, frameworks, databases, middleware, toolchains, English/certificates;
- Delivery Target: Position name, JD, campus recruitment/social recruitment, page count requirements, style preferences, whether photos are needed;
- Output Requirements: HTML save location, whether to export PDF at the same time, file naming and privacy handling.
缺失字段补问规则
Missing Field Follow-up Rules
- 最多一次补问 3 个最关键问题，优先问会改变模板和内容结构的问题：目标岗位、页数、是否已有完整简历/附件。
- 如果用户要求“先生成初稿”，不要等待所有字段齐全；用 标记姓名、时间、公司、成果数据等缺口。
待补充 - 教育、工作、项目的正式名称和时间不得代填；成果指标没有证据时写可核验的定性结果或 。
待确认 - 发现用户材料中有真实隐私信息时，只写入用户要求的简历文件，不写入 skill 模板、示例、README 或公开说明。
- 如果同一字段在多个来源里冲突，列出冲突项并请用户确认，不自行选择更“好看”的版本。
- Ask at most 3 most critical questions in one follow-up, prioritize questions that will change the template and content structure: target position, page count, whether a complete resume/attachment already exists.
- If the user requests "Generate a draft first", do not wait for all fields to be complete; mark gaps such as name, time, company, achievement data with .
To be supplemented - Formal names and times for education, work, and projects must not be filled in on behalf of the user; when there is no evidence for achievement indicators, write verifiable qualitative results or .
To be confirmed - When real privacy information is found in user materials, only write it into the resume file as required by the user, do not write it into skill templates, examples, README or public instructions.
- If the same field conflicts in multiple sources, list the conflicting items and ask the user to confirm, do not choose the "better-looking" version on your own.
模板选择矩阵
Template Selection Matrix
按“岗位 × 页数 × 风格 × 内容密度”选择模板。没有对应资源时，用后备模板复刻同类结构。
| 场景 | 推荐模板结构 | 适用内容密度 | 风格 |
|---|---|---|---|
| 后端开发 / Python / Java | A4 单页双栏或紧凑单栏，项目经历优先 | 中高：2-3 段项目/实习 + 技能栈 | 稳重、清晰、工程化 |
| 数据分析 / 算法 / AI 应用 | A4 单页或双页，项目和论文/实验结果优先 | 高：项目指标、模型、数据集、可视化较多 | 专业、证据导向 |
| 产品 / 运营 / 商务 | A4 单页，经历成果和业务指标优先 | 中：实习/活动/项目较均衡 | 简洁、结果导向 |
| 设计 / 新媒体 / 作品集岗位 | A4 单页视觉型或带作品链接结构 | 中低：强调作品入口和视觉层级 | 更有辨识度但不过度装饰 |
| 校招无实习或经历较少 | A4 单页双栏，教育、技能、项目补足版面 | 低到中：1-2 个项目 | 稳妥、留白合理 |
| 社招或经历较多 | A4 双页，工作经历按时间倒序 | 高：多段工作/项目/成果 | 稳重、信息密度高 |
默认决策：
- 后端开发岗位默认优先单页双栏：左侧放信息、技能、奖项，右侧放教育、实习和项目；
- 内容超过单页且压缩会损害可读性时，改为双页而不是把字号缩到不可读；
- 单页优先形成“身份定位—最强证据—核心经历—技能”的完整闭环；双页时先填实第一页，再让第二页承接次要经历，禁止为了模板结构过早分页；
- 用户明确要“稳妥版”时优先保守措辞和证据完整性；明确要“进取版”时可强化定位，但必须标注待补证据。
Select templates according to "Position × Page Count × Style × Content Density". If corresponding resources are not available, use the fallback template to replicate similar structures.
| Scenario | Recommended Template Structure | Applicable Content Density | Style |
|---|---|---|---|
| Backend Development / Python / Java | A4 single-page two-column or compact single-column, prioritize project experience | Medium to high: 2-3 projects/internships + tech stack | Steady, Clear, Engineering-oriented |
| Data Analysis / Algorithms / AI Applications | A4 single-page or double-page, prioritize projects and papers/experimental results | High: Abundant project indicators, models, datasets, visualizations | Professional, Evidence-oriented |
| Product / Operation / Business | A4 single-page, prioritize experience achievements and business indicators | Medium: Balanced internships/activities/projects | Concise, Result-oriented |
| Design / New Media / Portfolio Positions | A4 single-page visual type or structure with work links | Medium to low: Emphasize work entry and visual hierarchy | More recognizable but not over-decorated |
| Campus Recruitment with No Internship or Few Experiences | A4 single-page two-column, use education, skills, projects to fill the layout | Low to medium: 1-2 projects | Stable, Reasonable white space |
| Social Recruitment or Rich Experiences | A4 double-page, work experience in reverse chronological order | High: Multiple work/projects/achievements | Steady, High information density |
Default Decisions:
- For backend development positions, prioritize single-page two-column layout by default: left side for information, skills, awards; right side for education, internships and projects;
- When content exceeds a single page and compression would harm readability, switch to double-page instead of reducing font size to unreadable levels;
- Single-page should prioritize forming a complete closed loop of "Identity Positioning—Strongest Evidence—Core Experience—Skills"; for double-page, fill the first page first, then let the second page take secondary experiences, prohibit premature pagination for template structure;
- When the user explicitly requests a "safe version", prioritize conservative wording and evidence integrity; when explicitly requesting an "aggressive version", positioning can be strengthened, but must mark evidence to be supplemented.
默认排版
Default Typesetting
- 默认 A4，左右边距以模板为基准并保持稳定分页；
- 优先使用清晰的中文字体层级，避免过度装饰；
- 默认白底并使用一个主强调色；在首屏 1/4 页内用字号、字重、对齐和细线展示目标身份与最强公开证据，不默认使用满宽深色头部、卡片矩阵或成组标签；
- 页面内容必须可选中、可修改、可复制；
- 用户没有提供真实照片时使用虚构示例照片，并提醒替换；
- 不把用户真实个人信息写入插件的模板、示例或 README。
- Default A4 size, left and right margins based on templates and maintain stable pagination;
- Prioritize clear Chinese font hierarchy, avoid over-decoration;
- Default white background with one main accent color; within the first 1/4 of the screen, display target identity and strongest public evidence using font size, font weight, alignment and thin lines, do not use full-width dark headers, card matrices or grouped tags by default;
- Page content must be selectable, editable and copyable;
- Use fictional sample photos when the user does not provide real photos, and remind them to replace;
- Do not write the user's real personal information into the plugin's templates, examples or README.
Print-preview QA
Print-preview QA
交付 HTML 前必须检查打印预览或等价的 print media 渲染结果。检查项：
- A4 页面尺寸、页边距和分页稳定，没有多余空白页；
- 页面占用符合 页面平衡规则：单页不过空，多页的非末页先填实，末页没有可通过重排消除的大面积空白；
- 单栏/双栏结构符合模板选择，打印预览中不会被移动端 CSS 改成错误布局；
- 长姓名、邮箱、链接、项目标题和技能标签不溢出、不重叠、不遮挡后续内容；
- 照片比例正常，未被拉伸、压扁或裁切到关键区域；
- 工具栏、编辑按钮、调试提示在打印时隐藏；
- 中文字体可读，字号不低于正常投递可接受范围；
- 背景色、分割线和标签在开启“背景图形”后表现正常，关闭背景图形时仍可读。
如果无法自动打开浏览器或生成预览图，必须在交付说明中写明未完成自动 QA，并给用户明确的人工检查步骤。
Must check print preview or equivalent print media rendering results before delivering HTML. Check items:
- A4 page size, margins and pagination are stable, no extra blank pages;
- Page occupancy complies with Page Balance Rules: single page is not too empty, non-last pages of multi-page documents are filled first, no large areas of blank space on the last page that can be eliminated by rearrangement;
- Single-column/two-column structure conforms to template selection, will not be changed to incorrect layout by mobile CSS in print preview;
- Long names, emails, links, project titles and skill tags do not overflow, overlap or block subsequent content;
- Photo ratio is normal, not stretched, squashed or cropped in key areas;
- Toolbars, edit buttons, debugging prompts are hidden during printing;
- Chinese fonts are readable, font size is not lower than the acceptable range for normal delivery;
- Background colors, dividers and tags perform normally after enabling "Background Graphics", still readable when background graphics are disabled.
If unable to automatically open the browser or generate preview images, must state in the delivery instructions that automatic QA is not completed, and provide clear manual inspection steps for the user.
PDF 导出验收标准
PDF Export Acceptance Criteria
PDF 不是简单“能保存”即可。导出或指导用户导出时，按以下标准验收。本机装有 Edge/Chrome 时，可用零依赖脚本 scripts/export-resume-pdf.mjs 自动导出（， 让 PDF 纸张跟随模板 ，不受浏览器默认纸型影响）；浏览器打印另存为 PDF 作为兜底。
npm run export:pdf -- <html路径> --out <pdf>preferCSSPageSize@page- 文件页数符合预期：单页模板导出 1 页，双页模板导出 2 页，除非用户明确允许扩页；
- PDF 中没有工具栏、编辑虚线、浏览器页眉页脚、URL、日期或多余空白页；
- 页面为 A4，缩放建议 100%，页边距使用默认/无边距时均不破坏内容；
- 双栏、表格、标签、项目符号和分割线在 PDF 中位置正确；
- 文本可选中、可复制，不能把整页截图当成 PDF；
- 公开链接在纸面上仍可识别目的地：可见文字优先使用规范化 URL、DOI 或“域名/关键路径”（如 ），不能只显示“网站”“PAPER”“CODE”“点击查看”等失去上下文的标签；
github.com/user/repo - 不以 PDF 的隐藏点击区域代替可见地址。长链接应去掉无关追踪参数并允许自然换行，导出后从 PDF 文本中抽查关键域名或 DOI；
- 如使用照片，照片清晰且比例正确；如使用占位照片，交付说明提醒替换；
- 最终说明包含推荐浏览器设置：Chrome/Edge、另存为 PDF、A4、背景图形开启、页眉页脚关闭、缩放 100%。
PDF is not just "able to be saved". When exporting or guiding users to export, accept according to the following standards. When Edge/Chrome is installed locally, the zero-dependency script scripts/export-resume-pdf.mjs can be used for automatic export (, makes PDF paper follow the template's , not affected by the browser's default paper size); browser print save as PDF is the fallback.
npm run export:pdf -- <html path> --out <pdf>preferCSSPageSize@page- File page count meets expectations: single-page template exports 1 page, double-page template exports 2 pages, unless the user explicitly allows page expansion;
- No toolbars, edit dashed lines, browser headers/footers, URLs, dates or extra blank pages in the PDF;
- Page size is A4, recommended zoom is 100%, margins do not damage content when using default/no margins;
- Two-column layout, tables, tags, bullet points and dividers are positioned correctly in the PDF;
- Text is selectable and copyable, cannot use full-page screenshots as PDF;
- Public links are still identifiable on paper: visible text should use standardized URLs, DOIs or "domain name/key path" (e.g., ), cannot only display context-free labels such as "Website", "PAPER", "CODE", "Click to view";
github.com/user/repo - Do not use hidden clickable areas in PDF instead of visible addresses. Long links should remove irrelevant tracking parameters and allow natural line breaks, spot-check key domain names or DOIs from PDF text after export;
- If photos are used, they are clear and have correct proportions; if placeholder photos are used, remind users to replace them in the delivery instructions;
- Final instructions include recommended browser settings: Chrome/Edge, Save as PDF, A4, Background Graphics enabled, Headers and Footers disabled, Zoom 100%.
交付内容
Delivery Content
默认交付：可编辑 文件、使用的模板说明、资源/fallback 状态、print-preview QA 结果、各页内容占用比例、浏览器编辑方法和 PDF 导出方法。若用户同时需要经历改写，先调用 完成文字，再将确认后的内容放入简历。
.html/asuDefault delivery: Editable file, explanation of the template used, resource/fallback status, print-preview QA results, content occupancy ratio of each page, browser editing methods and PDF export methods. If the user also needs experience rewriting, first call to complete the text, then put the confirmed content into the resume.
.html/asu