resume-skill

Resume Skill — resume generation and beautification

Turn "I need a good-looking resume" into a stable process:All materials first flow into a standardized structured data format, then are rendered with a template. This way, switching templates is just changing the skin, and content is not lost; beautification and creation from scratch share the same second half.

Three first principles

Never fabricate. All experience, responsibilities, and numbers must come from content the user actually provides. You can guide, ask follow-up questions, help them articulate vague things clearly, and turn weak bullets into strong ones, but never invent companies, positions, achievements, or quantified numbers.Any number must be verified with the user, and if uncertain, mark [待确认] rather than guessing one.
Ask only one question at a time. Conversational resume building is an interview, not a questionnaire. Ask one question → wait for the answer → follow up accordingly. Never throw out a string of questions at once.
Structure first, then render. No matter which entry point it is, first organize the content into the fields defined by schema/resume-data.md , and only after confirming it is correct apply the template to produce HTML.

Routing: determine intent first when the user comes in

What the user says	Which process to follow
"Help me beautify my resume" / "revise my resume" / uploaded an existing resume (PDF/docx/txt/md)	Beautify an existing resume → `prompts/beautify.md`
"I don't have a resume yet, here is my LinkedIn" / posted a linkedin.com link	LinkedIn import → `prompts/linkedin-import.md`
"I don't have a resume, help me make one" / "help me make one through chat"	Conversational resume building → `prompts/interview.md`
"Switch to another template" / "this one doesn't look good"	When structured data already exists, directly re-render (see the rendering process below)

If you can't tell, just ask:

"Are youalready have a resume you want to beautify, orstart from scratch and make one? If from scratch, would you ratherpaste a LinkedIn linkand let me import it, orlet's chatand I'll ask you questions to draw it out?"

Beautify an existing resume

See prompts/beautify.md. Key points:

Readthe resume provided by the user (readable PDF / copied-and-pasted text / Word export). Claude can directly Read PDF.
Parseinto the fields of schema/resume-data.md , marking missing items as [缺失]。
Diagnose(against guides/writing-tips.md): which bullets lack quantified results, which are piles of responsibilities rather than achievements, layout/length/timeline issues, ATS risks. Provide a brief diagnostic checklist.
Ask for consent before changing content: ask the user, "Can I go ahead and strengthen these weak bullets? (without changing the facts, only the wording)". Only change them if the user agrees, and after changing them have the user confirm the numbers one by one.
Choose a template → render(see below).

LinkedIn import

See prompts/linkedin-import.md. Key point: The reality is that LinkedIn has a login wall, and directly scraping public URLs is often blocked. The process will first try WebFetch; if that fails, it guides the user to use LinkedIn's "Save to PDF" to export their profile or copy and paste the content of each section, then parse it into the schema.

Conversational resume building

See prompts/interview.md. One question, one answer, in the order of Contact Info → Target Role → Each Experience (Company/Title/Dates → What you did → Result numbers) → Education → Skills, dig into one section and structure it, then finally aggregate into the schema.

Rendering process (the latter half shared by all three entry points)

Confirm structured data: echo the organized resume-data content back to the user for confirmation (especially numbers).

Choose template: 12 sets, ask the user's preference (default recommendation is Classic/ATS, because it is the most reliable for mass applications):

Template	File	Suitable for	ATS
Classic / ATS	`templates/classic-ats.html`	Single column, no frills, machine-parsable, most reliable for mass applications to large companies	✅ Friendly
Ledger Academic Engineering	`templates/ledger.html`	LaTeX-style serif, company/dates aligned at both ends, nested bullets, software/data/engineering roles	✅ Friendly
Modern Sidebar	`templates/modern-sidebar.html`	Two columns + dark sidebar, strong modern feel	🟡 Average
Pillar Info Cards	`templates/pillar.html`	Enhancv style, blue accents + skill pills + icon achievements + language progress dots, product/marketing/PM	🟡 Average
Elegant Serif	`templates/elegant-serif.html`	Serif centered editorial style, humanities-leaning roles such as design/consulting/marketing	🟡 Average
Atelier Minimal	`templates/atelier.html`	Lots of whitespace + thin uppercase name + vertical line columns, design/creative/aesthetic roles	🟡 Average
Timeline	`templates/timeline.html`	Vertical timeline spine on the left, career growth trajectory visible at a glance	🟡 Average
Swiss Grid	`templates/swiss.html`	Swiss grid, bold Helvetica + red accents, design/brand/creative	🟡 Average
Executive	`templates/executive.html`	Navy serif, steady and weighty, finance/consulting/executive/senior leadership	🟡 Average
Editorial	`templates/editorial-banner.html`	Three-column editorial-style top + red serif + giant bottom name band, brand/content/editorial	🟡 Average
Photo Corporate	`templates/photo-corporate.html`	Dark banner + circular headshot, sidebar with skill progress bars + vertical timeline + References, marketing/project/business	🟡 Average
Photo Minimal Red Dot Avatar	`templates/photo-minimal.html`	Red accents + split serif name + circular headshot, sidebar Awards + Skills, design/creative/portfolio	🟡 Average

Template selection tips:Mass applications/passing machine screening → Classic/ATS or Ledger；Directly viewed by people/referrals/portfolio-oriented → the other sets are more impressive。

Render: read the selected template,keep its <style> unchanged, replace the example content with the user's real data, and delete any sections you don't need (each <section> in the template can be deleted as a whole block). Generate a self-contained single-file HTML.
Also output an editable version: also generate a <姓名>-resume-<模板>-editable.html, and add contenteditable + floating toolbar (see prompts/editable-version.md). When printing, edit highlights and the toolbar are automatically hidden, so the PDF output is clean.
Output: save both files as <姓名>-resume-<模板>.html and <姓名>-resume-<模板>-editable.html. By the user's global preference, save by default to /Users/yanliu/Desktop/Claude skills/(other users should save to the current directory or be asked).
Tell the user how to convert to PDF: open in browser → Cmd+P → choose "Save as PDF" as the destination → set margins to None/Default, check Background graphics → save. For the editable version, you can first click on the text in the browser to fine-tune it, then Cmd+P; the toolbar has a ready-made button.
Can swap templates and re-render: the structured data is already in hand, so if the user says "try switching to Modern," just read the other template set and re-render, with no need to re-collect.

Hard rules when rendering

One page preferred: under 10 years of experience should be kept to 1 page; senior candidates can use 2 pages. If content overflows, prioritize trimming bullets rather than shrinking it until it's unreadable.
Don't touch the template CSS: the template's layout/color scheme is already designed; only replace the content text. If the user wants to adjust colors, ask separately.
Delete empty sections as whole blocks: for sections that don't exist (such as Publications), delete them along with <section> , and don't leave an empty heading.
Real data: any placeholder numbers in the examples must be replaced with the user's real data or [待确认]; never leave template example numbers in the final product.
Contact info anonymization reminder: if the user wants to share it publicly, remind them whether the phone number/address needs to be masked.

Supporting files

schema/resume-data.md — standard structured fields (the interchange format for all workflows)
prompts/interview.md — conversational collection script
prompts/linkedin-import.md — LinkedIn import and fallback plan
prompts/beautify.md — existing resume parsing and diagnosis
prompts/editable-version.md — injection snippet to upgrade the final product into a browser-editable version
guides/writing-tips.md — bullet writing, quantification, ATS keywords, common mistakes
templates/*.html — 12 print-optimized templates