/resume: Create Editable Resume

Resource Location

1. Claude Code Installation Layout:

   ../../assets/asu/

   ;
2. Repository Plugin Layout:

   ../../assets/

   .

resume-data-template.json

resume-template-editable.html

resume-template-two-page.html

template-overview.jpg

fictional-resume-photo.png

templates-html/

• 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.

assets/asu/

assets/

• 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. 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

• 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

• 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

• 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

• 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

• 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.

PDF Export Acceptance Criteria

• 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

/asu