claude-resume-kit: Skill for Claude Code

/make-resume

User input: $ARGUMENTS

Parse $ARGUMENTS:

• File path (e.g., JDs/*.txt) → read that file for the JD
• Text after the path starting with "Focus:"/"Emphasize:"/"Downplay:" → focus directive
• "Quick:" prefix → Quick Mode (see below)
• Empty → ask the user for the JD
• Inline JD text (no file path) → save to JDs/temp_<company>.txt, proceed normally

---

Safety Rules (ALWAYS ENFORCED)

Accuracy > Relevance > Impact > ATS > Brevity

Read config.md Provenance Flags before generating any content. Verify every claim against that table.

• Use the email from config.md Personal Info in all outputs
• Resume bullets: ALL variable bullets are 2L (CV: 2L/3L mix OK, check config.md Document Preferences)
• Source ALL bullet content from resume_builder/experience/ files. Never fabricate.
• Run python3 resume_builder/helpers/char_count.py after each section — the tool is authoritative

---

User Input During Execution

If the user provides feedback, corrections, or suggestions at any point:

1. Acknowledge the input immediately
2. If it affects an already-written section: go back, fix it, re-run char count gate
3. If it changes the bullet plan: update session file Bullet Plan
4. If it's a question: answer it, then continue from current step
5. Never restart a phase — resume from current position

---

Startup

Read resume_builder/reference/shared_ops.md for session startup, file derivation, and organization protocols.

Then:

1. Read CLAUDE.md — check Active Sessions and KB Corrections
2. Read config.md — load Provenance Flags, email, document preferences, role types
3. If session file exists for this JD:
   • Read session file, check Status
   • Phase 0: DONE, Phase 1: PENDING → resume at Phase 1
   • Phase 1: DONE → resume at Budget Gate
   • Phase 2: IN_PROGRESS → read .tex, check what sections exist, resume from checkpoint
   • Phase 2: DONE → "Resume already done. Run /make-cl next." Show next command. Stop.
4. If no session file: proceed to Phase 0