Resume Builder
REQUIRED BACKGROUND: Use career-state-protocol. For a targeted resume, also use the T### model produced by jd-company-research.
Modes
- Master resume: create the durable, comprehensive source version from confirmed career evidence.
- Targeted resume: select and frame evidence for one supplied Target Model without changing the underlying facts.
- Audit: inspect an existing resume for unsupported claims, inconsistency, weak evidence, unclear ownership, and ATS content problems.
Do not bind content to LaTeX, Word, Typst, or another layout system. Produce clean semantic content unless the user separately requests document formatting.
Claim gate
Every substantive bullet must map to one or more C### claims with status source-supported, user-confirmed, or accurately scoped bounded. Never publish candidate, industry-inference, rejected, or stale content.
If the target asks for unsupported experience, record an evidence gap. Do not insert adjacent keywords as if they were delivered responsibilities.
Workflow
- Read the Career Profile, claim registry, project dossiers, and current resume variants.
- For targeted work, read the actual
T### capability model and source JD.
- Resolve title, date, scope, metric, stack, customer, ownership, and delivery-state conflicts.
- Select evidence by target relevance, strength, distinctiveness, recency, and follow-up safety.
- Draft concise bullets using action, mechanism, scope, and result where evidence permits.
- Preserve the candidate's actual seniority and contribution boundary.
- Run the Claim audit, target coverage review, ATS content check, and cross-artifact consistency review.
- Show high-risk wording changes and uncovered target requirements before finalizing.
Read references/resume-contract.md for output and references/audit-checks.md for validation.
Writing rules
- Prefer concrete products, systems, decisions, users, and outcomes over adjectives.
- Define metrics through baseline, time range, population, source, and attribution when relevant.
- Use target terminology only when it accurately describes confirmed work.
- Do not hide a prototype, proposal, benchmark, or supporting role behind stronger verbs.
- Keep bullets defensible under a two-level interview follow-up.
- Match the output language to the requested resume language or target context.
Final output
Return the resume content first, followed by a compact Claim audit, JD coverage summary when applicable, ATS findings, and unresolved G### items. Do not expose internal IDs inside the resume itself.
1---2name: resume-builder3description: Use when creating, auditing, strengthening, or tailoring resume content from a candidate's confirmed career state, with or without a specific job description.4---56# Resume Builder78**REQUIRED BACKGROUND:** Use `career-state-protocol`. For a targeted resume, also use the `T###` model produced by `jd-company-research`.910## Modes1112- **Master resume:** create the durable, comprehensive source version from confirmed career evidence.13- **Targeted resume:** select and frame evidence for one supplied Target Model without changing the underlying facts.14- **Audit:** inspect an existing resume for unsupported claims, inconsistency, weak evidence, unclear ownership, and ATS content problems.1516Do not bind content to LaTeX, Word, Typst, or another layout system. Produce clean semantic content unless the user separately requests document formatting.1718## Claim gate1920Every substantive bullet must map to one or more `C###` claims with status `source-supported`, `user-confirmed`, or accurately scoped `bounded`. Never publish `candidate`, `industry-inference`, `rejected`, or `stale` content.2122If the target asks for unsupported experience, record an evidence gap. Do not insert adjacent keywords as if they were delivered responsibilities.2324## Workflow25261. Read the Career Profile, claim registry, project dossiers, and current resume variants.272. For targeted work, read the actual `T###` capability model and source JD.283. Resolve title, date, scope, metric, stack, customer, ownership, and delivery-state conflicts.294. Select evidence by target relevance, strength, distinctiveness, recency, and follow-up safety.305. Draft concise bullets using action, mechanism, scope, and result where evidence permits.316. Preserve the candidate's actual seniority and contribution boundary.327. Run the Claim audit, target coverage review, ATS content check, and cross-artifact consistency review.338. Show high-risk wording changes and uncovered target requirements before finalizing.3435Read `references/resume-contract.md` for output and `references/audit-checks.md` for validation.3637## Writing rules3839- Prefer concrete products, systems, decisions, users, and outcomes over adjectives.40- Define metrics through baseline, time range, population, source, and attribution when relevant.41- Use target terminology only when it accurately describes confirmed work.42- Do not hide a prototype, proposal, benchmark, or supporting role behind stronger verbs.43- Keep bullets defensible under a two-level interview follow-up.44- Match the output language to the requested resume language or target context.4546## Final output4748Return the resume content first, followed by a compact Claim audit, JD coverage summary when applicable, ATS findings, and unresolved `G###` items. Do not expose internal IDs inside the resume itself.
ZhanlinCui