resume

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/resume:制作可编辑简历

/resume: Create Editable Resume

生成真正可编辑的中文 HTML 简历,而不是把简历截图嵌入页面。用户可以在浏览器中继续修改文字、照片、字体、颜色和加粗内容,并通过打印导出 PDF。
Generate truly editable Chinese HTML resumes instead of embedding resume screenshots into pages. Users can continue to modify text, photos, fonts, colors, and bold content in the browser, and export PDF via printing.

资源定位

Resource Location

ASu 资源支持两种布局,按以下顺序定位:
  1. Claude Code 安装布局:
    ../../assets/asu/
  2. 仓库插件布局:
    ../../assets/
只有候选目录同时包含
resume-data-template.json
resume-template-editable.html
resume-template-two-page.html
template-overview.jpg
fictional-resume-photo.png
,以及
templates-html/
下全部 18 个内置模板时才使用它,避免把其他 skill 的同名目录或不完整安装误判为 ASu 资源:
  • resume-data-template.json
    :匿名简历内容结构;
  • templates-html/
    :18 个中文 HTML 模板;
  • resume-template-editable.html
    :可编辑模板起点;
  • resume-template-two-page.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:
  1. Claude Code Installation Layout:
    ../../assets/asu/
    ;
  2. Repository Plugin Layout:
    ../../assets/
    .
Only use the candidate directory if it contains all of the following files:
resume-data-template.json
,
resume-template-editable.html
,
resume-template-two-page.html
,
template-overview.jpg
,
fictional-resume-photo.png
, and all 18 built-in templates under
templates-html/
. This avoids misjudging directories with the same name from other skills or incomplete installations as ASu resources:
  • resume-data-template.json
    : Anonymous resume content structure;
  • templates-html/
    : 18 Chinese HTML templates;
  • resume-template-editable.html
    : Editable template starting point;
  • resume-template-two-page.html
    : Two-page template starting point;
  • template-overview.jpg
    : Template preview image;
  • fictional-resume-photo.png
    : Fictional sample photo, only used for template demonstration.
If the skill is copied separately to another directory, first locate
assets/asu/
and
assets/
by moving upward from the current skill directory in sequence. Do not create template resources out of thin air.
If neither layout is found with complete resources after upward search, explicitly state "Template resources are not installed with the skill" and enable the fallback solution:
  • Priority is given to creating a concise A4 editable HTML, retaining browser editing, print toolbar hiding, and PDF export capabilities;
  • Do not promise 18 sets of templates, template preview images, sample photos, or original template replication accuracy;
  • 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 falsify missing resources as "official templates used".

工作流程

Workflow

  1. 先按“输入清单”盘点材料;缺少关键字段时按“缺失字段补问规则”补问,无法补齐时使用
    待补充
    待确认
    占位,不捏造经历。
  2. 如果用户上传 PDF、已有简历、截图、图片或文档,先提取内容并检查布局;截图类输入还要分析栏位、间距、字体层级、颜色、照片位置和分页,再重建为 HTML。
  3. 按“模板选择矩阵”选择模板、页数和风格;如果资源缺失,启用后备模板并说明限制。
  4. 输出 HTML 文件,保持文字和布局可编辑;工具栏放在页面外并在打印时隐藏。
  5. 把 print-preview 作为导出前强制 QA:打开或模拟打印预览,检查分页、双栏、照片比例、长文本溢出、中文字体、打印边距和 A4 纸张效果;发现问题先修复 HTML/CSS 再交付。
  6. 用户需要 PDF 时,按“PDF 导出验收标准”说明浏览器打印设置,或按用户要求生成 PDF;不要用截图替代可编辑源文件。
  1. First inventory materials according to the "Input Checklist"; follow the "Missing Field Follow-up Rules" to ask for missing key fields. Use
    To be supplemented
    or
    To be confirmed
    as placeholders when fields cannot be completed, do not fabricate experience.
  2. If the user uploads a PDF, existing resume, screenshot, image, or document, first extract the content and check the layout; for screenshot inputs, analyze fields, spacing, font hierarchy, colors, photo position, and pagination, then rebuild into HTML.
  3. Select the template, page count, and style according to the "Template Selection Matrix"; enable the fallback template and explain limitations if resources are missing.
  4. Output the HTML file, keeping text and layout editable; place the toolbar outside the page and hide it during printing.
  5. 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; fix HTML/CSS before delivery if issues are found.
  6. When the user needs a PDF, explain browser print settings according to the "PDF Export Acceptance Criteria", or generate the PDF as required by the user; do not use screenshots instead of editable source files.

输入清单

Input Checklist

先从用户消息、附件和项目文件里抽取已有信息,再只补问真正影响交付的缺口。
  • 基础信息:姓名、电话、邮箱、城市/籍贯、求职方向、个人主页/GitHub/作品集(可选);
  • 教育背景:学校、学历、专业、起止时间、GPA/排名、主修课程、奖项;
  • 实习/工作:公司或团队、岗位、起止时间、业务背景、个人职责、技术栈、结果证据;
  • 项目经历:项目名称、目标岗位相关性、个人边界、技术栈、核心动作、结果证据、可展示链接或截图;
  • 技能:语言、框架、数据库、中间件、工具链、英语/证书;
  • 投递目标:岗位名称、JD、校招/社招、页数要求、风格偏好、是否需要照片;
  • 输出要求:HTML 保存位置、是否同时导出 PDF、文件命名和隐私处理。
First extract existing information from user messages, attachments, and project files, then only ask for gaps that truly affect delivery.
  • Basic Information: Name, phone number, email, city/hometown, job target, personal homepage/GitHub/portfolio (optional);
  • Education Background: School, degree, major, start/end time, GPA/ranking, main 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;
  • Application Target: Position name, JD, campus recruitment/social recruitment, page count requirement, style preference, whether photo is needed;
  • Output Requirements: HTML save location, whether to export PDF simultaneously, 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 exists.
  • If the user requests "first generate a draft", do not wait for all fields to be complete; mark gaps such as name, time, company, and achievement data with
    To be supplemented
    .
  • Formal names and times for education, work, and projects cannot be filled in on behalf of the user; write verifiable qualitative results or
    To be confirmed
    when there is no evidence for achievement indicators.
  • When real privacy information is found in user materials, only write it into the resume file requested by the user, not into skill templates, examples, README, or public instructions.
  • If the same field conflicts across 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 / JavaA4 单页双栏或紧凑单栏,项目经历优先中高:2-3 段项目/实习 + 技能栈稳重、清晰、工程化
数据分析 / 算法 / AI 应用A4 单页或双页,项目和论文/实验结果优先高:项目指标、模型、数据集、可视化较多专业、证据导向
产品 / 运营 / 商务A4 单页,经历成果和业务指标优先中:实习/活动/项目较均衡简洁、结果导向
设计 / 新媒体 / 作品集岗位A4 单页视觉型或带作品链接结构中低:强调作品入口和视觉层级更有辨识度但不过度装饰
校招无实习或经历较少A4 单页双栏,教育、技能、项目补足版面低到中:1-2 个项目稳妥、留白合理
社招或经历较多A4 双页,工作经历按时间倒序高:多段工作/项目/成果稳重、信息密度高
默认决策:
  • 后端开发岗位默认优先单页双栏:左侧放信息、技能、奖项,右侧放教育、实习和项目;
  • 内容超过单页且压缩会损害可读性时,改为双页而不是把字号缩到不可读;
  • 用户明确要“稳妥版”时优先保守措辞和证据完整性;明确要“进取版”时可强化定位,但必须标注待补证据。
Select templates based on "Position × Page Count × Style × Content Density". Use fallback templates to replicate similar structures when corresponding resources are unavailable.
ScenarioRecommended Template StructureApplicable Content DensityStyle
Backend Development / Python / JavaA4 single-page two-column or compact single-column, project experience prioritizedMedium-high: 2-3 projects/internships + tech stackStable, clear, engineering-oriented
Data Analysis / Algorithm / AI ApplicationA4 single-page or two-page, projects and papers/experiment results prioritizedHigh:较多项目指标、模型、数据集、可视化较多Professional, evidence-oriented
Product / Operation / BusinessA4 single-page, experience achievements and business indicators prioritizedMedium: Balanced internships/activities/projectsConcise, result-oriented
Design / New Media / Portfolio PositionA4 single-page visual structure or structure with work linksMedium-low: Emphasize work entry and visual hierarchyMore recognizable but not over-decorated
Campus Recruitment with No Internship or Limited ExperienceA4 single-page two-column, education, skills, and projects to fill the layoutLow to medium: 1-2 projectsSafe, reasonable white space
Social Recruitment or Rich ExperienceA4 two-page, work experience in reverse chronological orderHigh: Multiple work/projects/achievementsStable, high information density
Default Decisions:
  • For backend development positions, single-page two-column layout is prioritized by default: left side for information, skills, awards; right side for education, internships, and projects;
  • Switch to two-page layout when content exceeds a single page and compression would harm readability, rather than reducing font size to unreadable levels;
  • Prioritize conservative wording and evidence integrity when the user explicitly requests a "safe version"; strengthen positioning when requesting an "aggressive version", but must mark pending evidence.

默认排版

Default Typography

  • 默认 A4,左右边距以模板为基准并保持稳定分页;
  • 优先使用清晰的中文字体层级,避免过度装饰;
  • 页面内容必须可选中、可修改、可复制;
  • 用户没有提供真实照片时使用虚构示例照片,并提醒替换;
  • 不把用户真实个人信息写入插件的模板、示例或 README。
  • Default A4 size, left and right margins based on templates with stable pagination;
  • Prioritize clear Chinese font hierarchy, avoid excessive decoration;
  • Page content must be selectable, editable, and copyable;
  • Use fictional sample photos when the user does not provide a real photo, and remind 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 the print preview or equivalent print media rendering result before delivering the HTML. Check items:
  • Stable A4 page size, margins, and pagination, no extra blank pages;
  • Single-column/two-column structure matches 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;
  • Normal photo ratio, not stretched, squashed, or cropped in key areas;
  • Toolbars, edit buttons, and debugging prompts are hidden during printing;
  • Chinese fonts are readable, font size not below the acceptable range for normal application;
  • Background colors, dividers, and tags perform normally after enabling "Background Graphics", still readable when background graphics are turned off.
If unable to automatically open the browser or generate a preview image, clearly 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 不是简单“能保存”即可。导出或指导用户导出时,按以下标准验收:
  • 文件页数符合预期:单页模板导出 1 页,双页模板导出 2 页,除非用户明确允许扩页;
  • PDF 中没有工具栏、编辑虚线、浏览器页眉页脚、URL、日期或多余空白页;
  • 页面为 A4,缩放建议 100%,页边距使用默认/无边距时均不破坏内容;
  • 双栏、表格、标签、项目符号和分割线在 PDF 中位置正确;
  • 文本可选中、可复制,不能把整页截图当成 PDF;
  • 如使用照片,照片清晰且比例正确;如使用占位照片,交付说明提醒替换;
  • 最终说明包含推荐浏览器设置:Chrome/Edge、另存为 PDF、A4、背景图形开启、页眉页脚关闭、缩放 100%。
PDF is not just "saveable". Follow the following standards for acceptance when exporting or guiding users to export:
  • File page count meets expectations: single-page template exports 1 page, two-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 100%, margins using default/no margins do not damage content;
  • Two-column layout, tables, tags, bullet points, and dividers are positioned correctly in the PDF;
  • Text is selectable and copyable, do not use full-page screenshots as PDF;
  • If photos are used, they are clear and in correct ratio; if placeholder photos are used, remind replacement in delivery instructions;
  • Final instructions include recommended browser settings: Chrome/Edge, Save as PDF, A4, enable Background Graphics, disable headers/footers, zoom 100%.

交付内容

Delivery Content

默认交付:可编辑
.html
文件、使用的模板说明、资源/fallback 状态、print-preview QA 结果、浏览器编辑方法和 PDF 导出方法。若用户同时需要经历改写,先调用
/asu
完成文字,再将确认后的内容放入简历。
Default Delivery: Editable
.html
file, template description used, resource/fallback status, print-preview QA result, browser editing method, and PDF export method. If the user also needs experience rewriting, first call
/asu
to complete the text, then place the confirmed content into the resume.