When the user inputs /asu-resume or "I want an ASu-style resume", follow the layout rules of references/asu-resume-template.md , use the shared resource ../../assets/asu-resume-template.html as a read-only master template, copy it, and generate the user's exclusive editable resume. It is strictly forbidden to directly modify the template source file; all names, experience, projects, and style customizations are written only into the newly generated user copy. The template corresponds to the single-column, high-density technical resume in the reference image: identity and contact information at the top, a reserved spot for an ID photo at the far right, blue section headings, light gray company experience bars, project-level technical points, and continuous two-page layout.
Routing boundaries
- To only rewrite experience, projects, or HR talking points: use
/asu； - For general resume creation and template selection: use
/make-resume； - When explicitly requesting ASu-style, template replication, or the corresponding HTML/PDF: use
/asu-resume。
Workflow
- Treat "I want an ASu-style resume" as invoking
/asu-resume; first copy the read-only template, then fill the user's information and experience into the copy, keeping the template file unchanged. - Read the resume, PDF, screenshots, project materials, or claims-evidence ledger provided by the user, and extract the real name, contact information, education, experience, projects, skills, and public links; when using the ledger, follow the status and handoff rules, and the final PDF uses only "confirmed" claims.
- First rewrite the experience as "target identity → project overview → personal responsibilities → technical actions → result evidence", then lay it out; do not embed screenshots directly into the resume.
- Match a brand logo for each experience where the company or platform name can be confirmed. Prefer reusing the shared resource
../../assets/logos/; when the shared directory does not have the corresponding brand, obtain the official SVG from@lobehub/iconsor@lobehub/icons-static-svg. Copy the actually used SVG into thelogos/directory next to the user's exclusive resume, and make the HTML use thelogos/<brand>.svgrelative path, to avoid loss after generation due to repository paths or network unavailability. Only keep a plain-text company bar when the brand cannot be confirmed or LobeHub has no available resource; do not fabricate or substitute a similar brand logo. - Generate a truly editable HTML; read the general icons for the personal information section from
../../assets/icons/, and keep a clickable upload or replace ID photo placeholder. The photo placeholder frame is shown only when editing and no photo has been uploaded yet; after a photo is uploaded and when printing, hide the border and prompt. The template toolbar provides two page modes:A4 分页for regular print pagination,A4 长页（不限高度）for single-page continuous editing; the same toolbar supports modifying font, font size, color, and bold after selecting text, provides undo/redo, automatically saves edited content to browser local storage, and can write the current content to a local file specified by the user through "Save HTML"; it also supports printing or exporting PDF. - For a single page, prioritize arranging "identity positioning—strongest evidence—core experience—skills" into a complete loop; when two pages are needed, first fill the first page fully, then put supplementary experience on the second page. Finally follow the
/make-resumeof A4 page balance and visual density QA Check page usage, Chinese fonts, long-text overflow, whether public links are recognizable in print, Logo proportions, and cross-page continuity.
Icon rules
When generating AI, model, platform, or company icons, prioritize following the LobeHub Icons skill instructions, using SVG resources from @lobehub/icons or @lobehub/icons-static-svg . Do not hand-draw existing brand icons, and do not replace scalable resources with low-resolution screenshots. User-specific Logos only need to be saved with the user copy; only when adding reusable Logos to the repository's shared resources should they be registered in the Logo table of references/asu-resume-template.md .
Common icons such as phone, email, WeChat, identity, education, and Star also use downloaded SVGs, not Emoji. Users can later place their ID photo into the reserved frame in the upper right corner of the template.
Content boundaries
- Keep formal job titles, companies, dates, and educational background; do not use the template to fabricate a higher job level.
- Every “Owner, led, architecture, 0→1, core author” must have evidence of responsibility, commits, launch, or review.
- Metrics such as total project calls, user counts, Stars/Forks, etc. must specify their scope and cannot automatically be counted as personal achievements.
- Use
【待补：指标/职责/链接】to mark uncertain information, and have the user verify it all together before finalizing.
Coordination with /asu coordination with
When the user only says “I want suhua,” you can first output the resume content and HR opening remarks, without forcing HTML generation. Only when the user explicitly says “replicate the same style,” “I want the Asu-style resume,” “make a resume file,” or enters /asu-resume , then copy the template and generate a user-specific editable resume file, without directly modifying the template.