make-resume

/make-resume: create and replicate an editable resume

/make-resume is the only entry point for creating resume files. By default, use the ASu single-column high-density technical resume template in the repository as the read-only master; when the user explicitly specifies another template, local HTML, template name, or reference screenshot, generate according to the specified template first. Regardless of which template is used, the deliverable must be genuinely editable HTML and support printing or exporting to PDF.

Routing boundaries

• Only rewriting experience, projects, or HR wording: use /great-resume；
• Creating, modifying, or replicating any HTML/PDF resume, or selecting a resume template: use /make-resume；
• "I want the same resume as Asu" is equivalent to selecting the default ASu template, and still uses /make-resume, and is no longer routed to another resume skill.

Templates and resources

The default template shell is assets/asu-resume/template.html。

Users can specify a template in the following ways, with higher priority than the default template:

1. Specify a repository template name or path;
2. Provide local HTML/Word/PDF/resume image as a reference;
3. Specify assets/templates-html/ the template shell file under that.

In the repository, assets/asu-resume/template.html and assets/templates-html/ are template shell files, and the shared outer frame is located in assets/frame/. The Agent only reads the content shell, and creates and modifies a copy in the user directory. The shell file contains only the design draft; before delivery, you must use scripts/ the script under that to inline the shared base.css、toolbar.css、toolbar.html and editor.js, generating self-contained HTML; the shell file must not be handed directly to the user. Reference screenshots are only used to analyze the layout and must not be embedded as full pages in the final resume.

If the skill is copied separately to another directory, first locate assets/upward from the current skill directory, and use it only when that directory contains complete template resources. Complete resources include at least resume-data-template.json、template-overview.jpg、fictional-resume-photo.png、frame/ under that, base.css、toolbar.css、toolbar.html、editor.js, and all 18 template shell files. If complete resources cannot be found, you must clearly state so, use a concise A4 fallback template, and explain that 18 sets of templates, preview images, sample photos, or the original template replication accuracy are not guaranteed.

Workflow

1. Inventory the name, contact information, education, internship/work, projects, skills, target position, public links, page count, and photo requirements in the user's message, attachments, and project files. When the user provides a claim-evidence ledger, read the facts according to ledger status rules .
2. If the user provides a PDF, an existing resume, screenshot, image, or document, first extract the text and analyze the columns, spacing, font hierarchy, colors, photo position, and pagination, then choose a template. If no template is specified, use the default ASu template; if a template is specified, do not replace it without authorization.
3. When key fields are missing, ask only about content that truly affects delivery. Names, schools, companies, positions, dates, and achievement metrics must not be fabricated; when they cannot be completed, use 待补充 or 待确认 as placeholders.
4. Use the "template selection matrix" to determine the page count and content order. If the content can form a complete single page at normal font size, prefer a single page; when two pages are needed, first fill the first page fully, then let the second page carry supplementary content, and do not paginate prematurely for the sake of template structure.
5. Generate user-exclusive editable HTML. First generate the user content shell based on the template shell, then execute in the repository root directory: for the default ASu template use node scripts/build-asu-resume.mjs <用户内容壳> <用户输出HTML>, for other templates use node scripts/inline-template.mjs <用户内容壳> <用户输出HTML>. The script completes the shared toolbar/styles/code inlining. Referenced images,icons/ and logos/ are delivered together according to the relative paths of the output HTML.
6. When the company or platform name can be confirmed, match the brand logo. Prioritize reusing the actual SVG in the shared assets/logos/ ; when the corresponding resource is missing, use the official SVG from @lobehub/icons or @lobehub/icons-static-svg , and place the user-exclusive logo in the logos/ directory next to the user copy. When the brand cannot be confirmed or no usable resource is available, use a plain-text company bar; do not substitute a similar logo.
7. Use print-preview as mandatory QA before delivery: check A4 paper, pagination, single/double columns, photo proportions, long text overflow, Chinese fonts, print margins, toolbar hiding, link recognizability, and company logo proportions, then according to A4 page balance and visual density QA measure the content occupancy of each page and save full-page screenshots. If problems are found, first fix the HTML/CSS.
8. According to PDF export acceptance criteria generate or guide the generation of the PDF; do not use screenshots to replace the editable source file.

The formal final draft only uses claims that are applicable to the current position and have the status "Confirmed"; "Pending confirmation" may only remain in internal drafts, and must be confirmed or deleted before exporting the final PDF. Claims that are "Expired" and "Not adopted" must not enter external materials.

Input checklist

• Basic information: name, phone, email, city/place of origin, job direction, personal homepage/GitHub/portfolio (optional);
• Education background: school, degree, major, start and end dates, GPA/ranking, major courses, awards;
• Internship/work: company or team, position, start and end dates, business context, personal responsibilities, tech stack, evidence of results;
• Project experience: project name, position relevance, personal boundaries, tech stack, core actions, evidence of results, public links or screenshots;
• Skills: languages, frameworks, databases, middleware, toolchains, English/certificates;
• Application target: position name, JD, campus recruitment/social recruitment, page count requirements, style preferences, whether a photo is required;
• Template preference: default ASu template, or the user-specified template file, template name, reference image;
• Output requirements: HTML save location, whether to also export PDF, file naming and privacy handling.

Rules for asking follow-up questions about missing fields

• Ask at most 3 most critical questions once, prioritizing questions that will change the template and content structure: target position, page count, whether a complete resume/attachment already exists;
• When the user requests generating a first draft first, do not wait for all fields to be complete; use 待补充 to mark gaps such as name, dates, companies and result data;
• The official names and dates of education, work, and projects must not be filled in on behalf of the user; when result metrics have no evidence, write verifiable qualitative results or 待确认；
• When real private information is found, only write it into the resume file requested by the user, and do not write it into skill templates, examples, README or public descriptions;
• When 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

When the user explicitly specifies a template, always use the specified template; when none is specified, use the ASu single-column high-density technical resume template by default.

Scenario	Recommended template structure	Applicable content density	Style
User requests the ASu style, AI/Agent/LLM technical positions	ASu A4 single-column high density, prioritizing projects and technical evidence	High: multiple internships/projects + tech stack	Professional, evidence-oriented
Backend development / Python / Java	A4 single-page two-column or compact single-column	Medium-high: 2—3 projects/internships + skill stack	Steady, engineering-oriented
Data analysis / algorithms / AI applications	A4 single page or two pages, prioritizing projects and experimental results	High: many metrics, models, datasets, and visualizations	Professional, evidence-oriented
Product / operations / business	A4 single page, prioritizing experience outcomes and business metrics	Medium: internships/activities/projects fairly balanced	Concise, results-oriented
Design / new media / portfolio positions	A4 single-page visual style or structure with portfolio links	Medium-low: emphasis on portfolio entry points and visual hierarchy	Distinctive but not overly decorative
Campus recruitment with no internship or little experience	A4 single-page two-column, with education, skills, and projects filling out the layout	Low to medium: 1—2 projects	Safe, reasonable use of white space
Experienced-hire or extensive experience	A4 two pages, work experience in reverse chronological order	High: multiple work/project/achievement entries	Steady, high information density

Default decisions:

• The default ASu template uses a single column, high density, blue section headings, light gray experience bars, and a photo placeholder in the upper right;
• When content exceeds one page and compressing it would harm readability, switch to two pages rather than shrinking the font to an unreadable size;
• A single page should prioritize forming a complete loop of "identity positioning—strongest evidence—core experience—skills";
• When the user explicitly requests a "safe version," prioritize conservative wording and complete evidence; when explicitly requesting an "aggressive version," the positioning may be strengthened, but evidence still to be supplemented must be marked.

Default layout

• Default A4, with left and right margins based on the selected template and stable pagination;
• Default white background with one primary accent color, avoiding excessive decoration;
• Page content must be selectable, editable, and copyable;
• When the user does not provide a real photo, a fictional sample photo may be used, with a reminder to replace it;
• Do not write the user's real personal information into the plugin's templates, examples, or README.

Print-preview QA

Before delivering HTML, the print preview or equivalent print media rendering result must be checked:

• A4 page size, page margins, and pagination are stable, with no extra blank pages;
• Page usage complies with the page balance rules: a single page is not too empty, non-final pages of multi-page documents are filled first, and the final page has no large blank area that can be eliminated by rearrangement;
• The single-column/two-column structure matches the selected template, and in print preview it will not be changed into an incorrect layout by mobile CSS;
• Long names, email addresses, links, project titles, and skill tags do not overflow, overlap, or obscure subsequent content;
• Photo proportions are normal, not stretched, squashed, or cropped into key areas;
• Toolbars, edit buttons, and debug hints are hidden when printing;
• Chinese fonts are readable, and the font size is not below the acceptable range for normal submissions;
• Background colors, dividers, and tags display normally when "Background graphics" is enabled, and remain readable when background graphics are disabled.

If the browser cannot be opened automatically or a preview image cannot be generated, the delivery notes must state that automated QA was not completed and provide manual inspection steps.

PDF Export Acceptance Criteria

When Edge/Chrome is installed locally, you can use the zero-dependency script scripts/export-resume-pdf.mjs to export automatically (npm run export:pdf -- <html路径> --out <pdf>，preferCSSPageSize makes the PDF paper follow the template @page); saving as PDF via browser printing serves as a fallback.

• The file page count matches expectations: a single-page template exports 1 page, and a two-page template exports 2 pages, unless the user explicitly allows page expansion;
• The PDF contains no toolbars, editing dashed lines, browser headers/footers, URLs, dates, or extra blank pages;
• The page is A4, the recommended zoom is 100%, and using default or no margins does not damage the content;
• Two-column layouts, tables, tags, bullet points, and dividers are positioned correctly;
• Text is selectable and copyable; a full-page screenshot must not be used as the PDF;
• Public links still allow the destination to be identified on paper, and must not show only context-free labels such as "Website", "PAPER", or "CODE";
• Long links have irrelevant tracking parameters removed and are allowed to wrap naturally; after export, spot-check key domains or DOIs from the PDF text;
• If a photo is used, it is clear and correctly proportioned; if a placeholder photo is used, the delivery notes remind the user to replace it;
• Recommended browser settings: Chrome/Edge, Save as PDF, A4, background graphics enabled, headers and footers disabled, zoom 100%.

LaTeX Output (Optional)

For users who are accustomed to LaTeX or need to continue maintaining their resume in Overleaf,.tex is anoptional additional format that does not replace the HTML delivery. It is generated only when the user explicitly requests LaTeX,.tex or an Overleaf version; the default delivery process remains unchanged.

• The template specification method is the same as for HTML. If unspecified, the default ASu single-column layout is used; when the user specifies another .tex master, pass the master path as the third argument to the script. Currently, assets/latex-resume/ provides three layouts:
  • template.tex: ASu single-column high density, blue section headings, consistent with the default HTML template's look, used when unspecified;
  • compact.tex: compact single-column, with tightened margins and line spacing and section headings using color blocks, suitable for candidates with more experience who need to fit onto one page;
  • academic.tex: academic style, no color, small caps headings, loose line spacing, black-and-white printing friendly, suitable for research and faculty applications. All three use only packages included in the TeX Live basic distribution.assets/templates-html/ Among the 18 HTML templates under .tex , explain this boundary and recommend the closest layout above.
• Information is equivalent; layout is not equivalent. .tex Ensure the chapter order and content are consistent with the HTML; pixel-perfect replication of the ASu style is not promised.
• ID photo and school logo. In the data, profile.photo specifies the image filename, the header is automatically split into two columns with text on the left and image on the right; when empty, it degrades to a plain text single column. Image filenames may only contain letters, digits, dots, underscores, and hyphens (\includegraphics filename parameters are not escaped), and when delivering, the image file and .tex must be given to the user together. The template is fault-tolerant to missing images: when the file is not found, it draws a placeholder box and gives a prompt, and will not interrupt compilation.
• The repository does not compile LaTeX, nor does it require users to install TeX. The output is a plain text source file; compilation is left to Overleaf or the user's existing local environment.

Generation method: first write the confirmed resume facts as structured JSON (for fields see ../../assets/resume-data-template.json, entire sections corresponding to omitted fields are not output), then execute in the repository root directory node scripts/build-latex-resume.mjs <简历数据JSON> <用户输出TEX> [母版TEX]. When the third parameter is omitted, the default ASu template is used, which is consistent with the way inline-template.mjs has the caller specify the shell file. Any @ containing all .tex markers can be used as a template: layout differences are concentrated in the template preamble, and the script's escaping and section generation logic is independent of layout and can be reused by each layout.

The default template is ../../assets/latex-resume/template.tex, and the script handles LaTeX escaping uniformly. To add a new layout, you only need to add under assets/latex-resume/ a @ that contains all \asuphotowidth、\asuheadtextwidth、\asuphoto、\asuname、\asumeta、\asuentry markers and defines .tex, without modifying the script; tests will automatically traverse that directory to validate the new layout. Do not bypass the script and hand-write .tex: in the resume body, C++、30%、snake_case、A&B and other content, if not escaped, will directly cause compilation to fail.

When delivering .tex , you must attach the Overleaf usage steps (three steps): ① New Project → Blank Project, fill in the Project name and then Create; ② Upload .tex, and when using an ID photo or school logo, upload the images to the same project as well; ③ In File → Settings, select this file as the Main document and choose XeLaTeXas the Compiler (required for Chinese; pdfLaTeX will fail), then Recompile. The template only uses packages bundled with the basic TeX Live distribution and does not specify a Chinese font (falling back to Overleaf's built-in Fandol), to ensure reproducible compilation across environments.

Deliverables

By default, deliver the editable .html file, the template instructions used, resource or fallback status, print-preview QA results, the content occupancy ratio of each page, the browser editing and saving method, and the PDF export method. If the user also needs experience rewriting, first call /great-resume to complete the text, then put the confirmed content into the user copy generated by /make-resume ; the default ASu template or the user-specified read-only template source file must not be modified.