The Job Search Playbook

I'm job hunting. Research [Company] for me: what they do, how they
make money, recent news and launches, team culture, who leads the
team I'd likely join, and what they're struggling with that someone
in a [your role type] seat could help fix. Check their careers page
for open [role type] roles. Finish with two answers: is this company
worth my time, and what should I say to my contact who works there?

1. Make the folders:

   mkdir -p ~/.claude/skills/resume-jd-tailor

2. Save the skill text (next section) as:

   ~/.claude/skills/resume-jd-tailor/SKILL.md

3. Write your own house rules file at:

   ~/.claude/RESUME_RULES.md

   Start from Andrew's real rules (below) and swap his specifics,
   project names, links, job titles, for your own equivalents.

4. Open Claude Code, hand it your master resume and a JD, and say:
   "Tailor my resume to this job description."

---
name: resume-jd-tailor
description: Take an existing resume as the template and tailor it
  to match a specific job description. Use when the user says
  "tailor my resume", "format my resume to this JD", "match my
  resume to this job", or provides a resume plus a job posting.
  Preserves the template's structure and styling, rewrites content
  to mirror the JD's language and priorities.
---

# Resume JD Tailor

Tailor a resume to a job description using the existing resume as
the template. The template's layout, sections, and styling are the
contract, only the content moves.

## Inputs

1. Template resume, the user's master resume.
2. Job description, pasted text, a file, or a URL to fetch.
3. House rules: ALWAYS read ~/.claude/RESUME_RULES.md first and
   follow every rule in it. Those rules override this skill.

## Process

### 1. Parse the JD
- Extract the role title, team, and the top 6-8 requirements in
  the JD's own words.
- Note the exact vocabulary the JD uses. Mirror their terms,
  recruiters and AI screeners match on them.

### 2. Map evidence
- For each requirement, find the strongest matching bullet,
  project, or story in the template resume.
- Flag requirements with thin evidence, tell the user rather than
  inventing experience. Never fabricate or relocate
  accomplishments to a different employer.

### 3. Rewrite the summary as the cover letter
Cover letters are out, summary intros are in. The summary at the
top of the resume does the cover letter's job: who you are, the
one proof point that matters for THIS role, why this role.
Max 2 lines.

### 4. Tailor the body
- Reorder bullets so the strongest JD matches appear first.
- Rewrite bullets to lead with the JD's language, staying truthful.
- Keep it AI-screener friendly: standard section headings, plain
  formatting, exact keyword matches, quantified outcomes.

### 5. Audit before delivering
- Verb audit: no repeated starting verbs across the whole resume.
- Line audit: every bullet fits one line, resume fits one page.
- Link audit: all links real and working, never placeholder #.
- Re-check every rule in ~/.claude/RESUME_RULES.md.

## Output

- Same format as the template (Markdown in, Markdown out).
- Name it Resume_<Company>_<Role> next to the template.
- Close with a short gap report: which JD requirements are strong,
  which are thin, so the user knows what to prepare a
  forward-looking interview answer for.

# Resume Generation Rules

When generating or tailoring a resume, ALWAYS follow these rules:

1.  Unique starting verbs - No verb repetition across the entire
    resume. Run a verb audit every time.
2.  No "philosophy" in Educator bullet - Never use the word
    "philosophy" in the Educator line under Thought Leadership.
3.  Commas instead of em dashes - Use commas, not em dashes, in
    bullet points.
4.  All bullets must fit on 1 line - No wrapping. If a bullet is
    too long, trim it.
5.  Resume must fit on 1 page - Use tight CSS spacing and concise
    language.
6.  DocOps full title - "DocOps Governance Workbench | Automated
    Copy Compliance Tool | Python, LangChain"
7.  Four core projects - SAGE, DocOps Governance Workbench,
    QuickRamp, YouTube Shorts Pipeline. Always include all four.
8.  No "AI Governance Framework" - Removed from all future
    generations (duplicate of DocOps).
9.  Darden PM Specialization - Include "Product Management
    Specialization (Darden)" where relevant.
10. Cisco listed as Splunk - The Cisco/Splunk manager role should
    say "Splunk", not "Cisco". End date is "Jan 2026".
11. Working links - LinkedIn, portfolio, and article links must be
    real URLs, never placeholder # hrefs.
12. SAGE subtitle - Always include "Hackathon Winner | Figma Make,
    Pinecone, Veo 3" in the SAGE project subtitle.
13. Summary max 2 lines - The resume summary section must not
    exceed 2 lines.

## Cover Letter Rules

1. No Workday mentions - Never reference Workday in cover letters.
   Focus on Splunk experience only.
2. Commas instead of em dashes - Use commas, not em dashes,
   throughout cover letter text.

Rules 2, 6-12 are Andrew-specific. Keep the pattern, replace the
content: pin YOUR core projects, YOUR exact titles, YOUR links,
and any correction you find yourself making twice.

Read this job description: [paste the JD]. Draft three capstone
project ideas I could build in about a week of evenings. Each idea
must map to skills the posting actually asks for. For each one give
me: the JD skills it proves, what it is in two sentences, and the
demo moment I would show in an interview. Then help me pick one and
turn it into a working plan with milestones.

Create a professional personal portfolio page as a single HTML file.
Use clean, modern styling. Include:

Header: [Full Name], [Professional Title/Tagline]
About: [2-3 sentence professional summary]
Experience Highlights: [3-5 key accomplishments with context]
Skills & Expertise: [core competencies organized by category]
What I Bring: [what makes you valuable, your unique combination of
experience, perspective, and capabilities]
Contact: [Email, LinkedIn, or however you want to be reached]

Design notes: professional color palette, readable fonts, good
spacing. No stock photos. Clean and confident. Save as portfolio.html.

Then iterate: "change the palette to navy and white", "add a section
for the capstone project with a screenshot", "make it less corporate,
more personal".

You are my interview-prep coach for the [Company] [Role] position.
Use the sources I have added: the job description, my tailored
resume, and my STAR stories.

Build me a study guide that:
1. Lists the top eight requirements from the job description, in
   the team's own words.
2. For each requirement, names the strongest matching evidence from
   my resume and the STAR story that proves it. Keep each story tied
   to the company where it happened.
3. Flags any requirement where my evidence is thin, so I know where
   to prepare a forward-looking answer instead of a past-tense one.

Then draft likely interview questions:
- Five behavioral questions this panel would ask, each tagged with
  the STAR story I should answer it with.
- Three technical questions about the core skills in the posting.
- One curveball about handling disagreement, with the story to use.

For the Audio Overview: focus the conversation on how my background
maps to this specific role. Spend the most time where the match is
strongest, and close with the gaps I should address out loud in the
interview rather than hope nobody notices.