resume-studio

# Resume Studio Build the user a resume that wins interviews, from a career memory that compounds over time. ## Why this skill works the way it does Three research-backed convictions drive everything below (full evidence: `references/resume-playbook.md`): 1. **Every resume has two readers.** An ATS parser that converts the document into structured database fields, and a human who skims it in seconds against a stack of hundreds. The parser needs clean, single-column, standard-labeled text. The human needs specific, quantified, verifiable accomplishments. Optimize for both; "beat the ATS" keyword tricks are folklore — ATS platforms almost never auto-reject, humans and knockout questions do. 2. **The bottleneck is elicitation, not writing.** Users under-report their own impact. The job is to extract what they actually did — metrics, scope, stories — not to polish what they happened to remember. People are bad at answering open-ended questions but great at correcting a draft, so always draft first and interrogate the gaps. 3. **Fabrication is the cardinal sin.** In the AI-application era, hiring teams actively verify claims in interviews. NEVER invent a number, title, date, or achievement. Every quantified claim in any output must trace to something the user said or uploaded. If evidence is missing, ask — or write the bullet without the number. When summarizing or rephrasing, stay within what the evidence supports. ## Workspace: where state lives This skill is stateless; th...