Resume

Workflow

Phase 1: Welcome & Input Collection

Start with this message:

Let's build your resume! I can work with whatever you have.

**How would you like to get started?** (pick one or more)

1. **Upload your current resume** — I'll read your PDF or Word doc and use it as a starting point
2. **Upload your LinkedIn PDF** — Save your LinkedIn profile as PDF and share it
3. **Share your GitHub username** — I'll pull your repos, languages, and project highlights
4. **Just answer questions** — I'll interview you and write everything from scratch

You can combine these — for example, upload a resume AND share your GitHub.

What works for you?

Wait for the user's response. Then:

If they chose option 1 (Resume upload):

• If they provide a file path, run the parser script:

  node "${CLAUDE_SKILL_DIR}/scripts/parse-resume.mjs" "<file_path>"
  

• The script outputs extracted text to stdout. Read and analyze the text yourself to extract: contact info, work history, education, skills, projects, certifications.
• Confirm what you extracted: "Here's what I found in your resume: [summary]. Does this look right?"

If they chose option 2 (LinkedIn PDF):

• Ask them to share the file path to their LinkedIn PDF
• Run the parser:

  node "${CLAUDE_SKILL_DIR}/scripts/parse-linkedin-pdf.mjs" "<file_path>"
  

• Parse the extracted text yourself. LinkedIn PDFs have a specific structure: Contact section (sidebar), Summary, Experience, Education, Skills, Certifications.

If they chose option 3 (GitHub):

• Ask for their GitHub username
• Run the fetcher:

  node "${CLAUDE_SKILL_DIR}/scripts/fetch-github.mjs" "<username>"
  

• The script outputs JSON with profile info, top repos (by stars), languages, and topics. Use this to populate: skills, projects, bio, and links.

If they chose option 4 (Questions only):

• Skip to Phase 2 immediately.

Merging multiple sources: If the user provides multiple sources, merge them intelligently:

• Use the most complete/recent version of each field
• Combine skills from all sources (deduplicate)
• Projects from GitHub complement work history from resume/LinkedIn
• Always prefer user-provided descriptions over auto-generated ones

After parsing, show a brief summary: "Here's what I have so far:" and list what you found for each section.

Phase 2: Gap-Fill Interview

Based on what you have (or don't have), ask targeted questions. Don't ask questions you already have answers for.

Always ask:

1. "What role are you targeting? (e.g., Senior Frontend Engineer, Product Manager, Full-Stack Developer)" — This shapes the entire resume tone.
2. "Is there a specific job description you're tailoring this for? If so, paste it and I'll optimize for it."

Ask if missing:

For contact info gaps:

• "What city/region should I list? (or 'Remote')"
• "What email should I put on the resume?"
• "LinkedIn URL?"

For each work experience (if descriptions are weak or missing):

• "At [Company], what was the most impactful thing you built or shipped?"
• "What problem were you solving? What was the outcome?"
• "Did you lead or mentor anyone? How big was the team?"
• "Any technologies worth highlighting from this role?"

For career summary (if not provided):

• "In one sentence, how would you describe yourself professionally?"
• "What's your biggest professional strength?"

For skills:

• "Are there any skills you want to highlight that aren't already captured?"
• "Any skills you want to remove or downplay?"

For projects (especially for early-career):

• "Any side projects, open source contributions, or hackathon wins worth including?"

Do NOT ask:

• Generic questions like "Tell me about yourself"
• Questions you already have answers for from the parsed data
• More than 3-5 questions total — keep it focused

Phase 3: Resume Generation

Generate the resume as a Markdown file with this structure:

# [Full Name]

[Email] | [Phone] | [Location]
[LinkedIn URL] | [GitHub URL] | [Portfolio URL]

---

## Summary

[2-3 sentences. First-person is OK. Mention years of experience, core expertise, and what you're looking for. Tailored to target role.]

---

## Experience

### [Job Title] — [Company]
*[Start Date] – [End Date or Present]* | *[Location]*

- [Achievement/responsibility bullet — start with strong verb, describe what you did and the impact]
- [Another bullet — vary the structure, don't be repetitive]
- [3-6 bullets per role, more for recent roles, fewer for older ones]

### [Previous Job Title] — [Company]
*[Start Date] – [End Date]* | *[Location]*

- [Bullets...]

---

## Education

### [Degree] in [Field] — [University]
*[Graduation Year]* | *[Location]*
[GPA if > 3.5 and < 3 years out of school]

---

## Skills

**Languages:** [list]
**Frameworks:** [list]
**Tools:** [list]
**Other:** [list]

---

## Projects

### [Project Name]
[1-2 sentence description. What it does, what tech you used, any notable outcomes.]
[Link if available]

---

## Certifications

- [Cert Name] — [Issuer] ([Year])

Writing guidelines:

• Read references/resume-best-practices.md for detailed writing rules
• Use reverse chronological order for experience and education
• Most recent role gets 4-6 bullets, older roles get 2-3
• Skills should be categorized (Languages, Frameworks, Tools, Cloud, etc.)
• Only include sections that have content — don't add empty sections
• One page for < 10 years experience, two pages max for senior roles

If a job description was provided:

• Mirror key terms from the JD naturally in your bullets
• Ensure required skills appear in the Skills section
• Adjust the summary to align with what the JD emphasizes
• Don't force it — if the user doesn't have a skill, don't fake it

Phase 4: Save & Preview

1. Create the output directory:

   mkdir -p ./resume-output
   

2. Save the Markdown resume:

   • Write to ./resume-output/resume.md

3. Save the structured data (for future edits):

   • Write to ./resume-output/resume-data.json with the structured resume data

4. Show the full resume in the conversation for the user to review.

5. Ask: "How does this look? Would you like me to adjust anything, or shall I generate the PDF and Word versions?"

Phase 5: Refinement Loop

The user may ask for changes. Common requests:

• "Make the summary shorter/longer"
• "Add more detail to the [Company] role"
• "Remove the projects section"
• "Tailor this for [job posting]"
• "Make it fit on one page"
• "Rephrase the bullet about [topic]"

Apply changes, update both resume.md and resume-data.json, and show the updated version.

Phase 6: Export

When the user is ready for final export:

PDF Generation:

cd "${CLAUDE_SKILL_DIR}/scripts" && node generate-pdf.mjs "$(pwd)/../../../../resume-output/resume.md" "$(pwd)/../../../../resume-output/resume.pdf"

If the script fails (missing dependencies), fall back:

cd "${CLAUDE_SKILL_DIR}/scripts" && npm install && node generate-pdf.mjs "$(pwd)/../../../../resume-output/resume.md" "$(pwd)/../../../../resume-output/resume.pdf"

DOCX Generation:

cd "${CLAUDE_SKILL_DIR}/scripts" && node generate-docx.mjs "$(pwd)/../../../../resume-output/resume.md" "$(pwd)/../../../../resume-output/resume.docx"

Tell the user where the files are saved:

Your resume is ready! Files saved to ./resume-output/:
  - resume.md (Markdown — easy to edit)
  - resume.pdf (PDF — for submitting applications)
  - resume.docx (Word — for ATS systems that prefer DOCX)
  - resume-data.json (structured data — for future updates)

Edge Cases

• No work experience: Focus on projects, education, skills, and certifications. Frame projects as professional experience.
• Career changer: Emphasize transferable skills. Use the summary to bridge the gap between old and new career.
• Gaps in employment: Don't draw attention to gaps. If the user brings it up, suggest filling with freelance work, volunteering, or learning (if applicable).
• Very long career (15+ years): Summarize older roles in 1-2 lines. Focus detail on last 10 years.
• Multiple short stints: Group similar contract roles if possible. Don't judge — just present them cleanly.

What NOT to Do

• Don't invent metrics, companies, or accomplishments
• Don't use "References available upon request"
• Don't include age, photo, marital status, or nationality
• Don't use buzzwords without substance ("results-driven", "team player", "passionate")
• Don't add an "Objective" section (use "Summary" instead)
• Don't list every technology you've ever touched — curate for relevance
• Don't use first person ("I built...") in bullet points — use implied first person ("Built...")