# Resume HTML Generation Guide You will generate HTML for the `` of a resume PDF. The wrapper HTML/CSS is already applied - you only output the body content. ## CSS Classes Available These classes are pre-defined and styled. Use them exactly as shown: ### Header ```html

FULL NAME

email@example.com | 555-123-4567 | linkedin.com/in/username | github.com/username
``` The contact line automatically wraps to a second line if there are many items — no extra CSS needed. ### Sections ```html

SECTION NAME

``` ### Summary ```html
Summary text goes here. Keep it concise and impactful.
``` ### Experience/Education Entry **IMPORTANT: Company and title go on ONE line, date on the right:** ```html
Company Name - Job Title
``` For education: ```html
University Name - BS Computer Science
``` ### Skills Use `` for category labels (NOT markdown `**bold**`): ```html
Languages: Python, JavaScript, TypeScript, Go
Frameworks: React, Node.js, FastAPI, Django
Tools: PostgreSQL, AWS, Docker, Kubernetes
``` ### Projects ```html
Project Name - Brief description
``` ### Simple Lists (Certifications, Publications) ```html ``` For publications: include DOI in parentheses at the end if available. ## Visual Criteria - **Font size:** 11pt-14pt range (body 11pt, name 14pt) - readable at arm's length - **Margins:** ~0.5in all sides (already set in wrapper) - **Length:** Single page preferred, 2 pages max - **Section headers:** Clear uppercase with underline - **Spacing:** Consistent gaps between entries ## Layout Guidelines 1. **One page preferred** - Be concise. Remove less relevant content if needed. 2. **Fill the page** - Aim to use the full page without overflow. 3. **Section order** - Typical order: Summary, Experience, Education, Skills, Projects, Certifications, Publications. Adjust based on relevance to job. 4. **Bullet points** - Max 3-5 per job. Focus on impact, not tasks. Include metrics. 5. **Dates** - Use consistent format (e.g., "Jan 2020" or "2020"). 6. **Entry layout** - Company/title on ONE line with date right-aligned (never stacked). ## Professional Standards ### Formatting - Consistent date format throughout (all "Jan 2020" or all "01/2020", not mixed) - Parallel structure in bullets (all start with past-tense verbs, or all present-tense) - No orphan lines (single line alone at top/bottom of page) ### Language - No first person ("I", "my", "me") - Active voice, strong verbs ("Led", "Built", "Reduced" not "Was responsible for") - No fluff words ("various", "helped with", "assisted in") - No slang or casual tone ### Content - Each bullet has: Action + Context + Result (ideally quantified) - No generic statements ("team player", "hard worker") - Specific technologies named, not "various tools" ### Visual Balance - Balanced whitespace - no section looks cramped or empty - Alignment consistent (all dates right-aligned, all bullets same indent) - No walls of text - max 3 lines per bullet ## Content Rules - Show concrete results with metrics when available - Feature keywords matching job requirements - Prioritize experiences most relevant to the role - Preserve original writing style where possible - Include all URLs from original resume ## What NOT to Do - Never add `