Resume Tailor Generic

2. Choose the tailoring depth

Use lightweight tailoring when the user gives:

• a title only
• a role family such as frontend, backend, product, platform, data, or AI
• a stack target such as React, Go, Python, or Node.js

Use deeper tailoring when the user gives:

• a pasted job description
• a job-description file
• a job-post URL

Deeper tailoring still follows the same evidence discipline. The difference is stronger emphasis matching, keyword coverage, and bullet ordering.

3. Tailor markdown first

Create a new variant next to the source resume with this basename pattern:

• resume-<slug>.md

Change only the parts that should move for the target:

• headline
• summary
• core skills
• experience bullet emphasis and ordering
• selected projects

Keep chronology, employers, dates, and factual scope stable unless the user explicitly asks for a larger rewrite.

Tailoring Rules

• Reuse strong, evidence-backed bullets before inventing new phrasing.
• Do not fabricate metrics, team sizes, revenue, performance claims, or project scope.
• Prefer clearer nouns and verbs over stacked seniority adjectives.
• Remove sourcing notes, TODOs, and internal commentary from the final resume text.
• Keep the layout single-column and ATS-safe unless the user explicitly asks for a styled variant.
• If a job description is supplied, mirror the role language where truthful, but do not keyword-stuff.
• If the workspace includes an evidence file, use it to strengthen support for claims, not to expand beyond what can be defended.

Output Naming

Use a stable lowercase hyphenated basename across artifacts:

• resume-senior-backend.md
• resume-senior-backend.docx
• resume-senior-backend.html
• resume-senior-backend.pdf

Prefer short, role-shaped slugs. Avoid company names in the basename unless the user asks for employer-specific versions.

Export

Use scripts/render_resume_outputs.py when the user wants deterministic .docx and .html output from markdown.

Example:

python3 /path/to/resume-tailor-generic/scripts/render_resume_outputs.py \
  ./resume-senior-backend.md \
  --css ./resume.css

This writes adjacent outputs:

• resume-senior-backend.docx
• resume-senior-backend.html

If pandoc is unavailable, stop at markdown and tell the user what is missing.

For PDF creation, print the generated HTML with Playwright or another browser-based print path when available. Use:

• letter size unless the user asks otherwise
• print background enabled when CSS styling matters
• conservative margins suitable for ATS parsing

Verification

After tailoring or export:

• verify the final resume has no invented claims
• verify the output filenames share the same basename
• verify the PDF stays at one page unless the user asked for more
• verify extracted text remains readable when PDF tools are available

Use pdfinfo and pdftotext when present. If those tools are missing, report the gap instead of guessing.

Scope Boundaries

• This skill is for resume tailoring first.
• If the user wants a strict recruiter-style fit assessment, use a resume evaluation workflow or a separate resume-review skill.
• If the user wants a cover letter, treat that as adjacent work rather than the default path.

Resources

references/source-discovery.md

Read this when you need candidate filenames, ambiguity resolution rules, or default naming conventions for tailored outputs.

references/export-checks.md

Read this when you need a compact checklist for export behavior, PDF verification, or ATS-safe formatting constraints.

scripts/render_resume_outputs.py

Deterministic renderer for markdown to .docx and .html. It requires pandoc and does not create the PDF.