Resume
Produce a one-page CV or résumé as a single HTML document sized for A4 or US Letter.
Structure
Order is fixed. Bold = required. Any required section that would be a single bullet → merge or drop.
| Section |
Contents |
Length |
| Header |
Name, one-line role/focus, contact (email + 1–2 links), location |
2–4 lines |
| Summary |
One or two sentences: what they do and for whom |
≤ 40 words |
| Experience |
Reverse chronological. Per entry: role, company, location (opt), dates, 3–5 result-focused bullets |
Fills the page |
| Projects |
Only if Experience is thin or the role demands it |
2–4 entries |
| Skills / Tools |
Grouped (Languages, Frameworks, Tools, …), not a wall of commas |
3–6 groups |
| Education |
Degree, school, year. Relevant coursework only if junior |
1–2 lines / entry |
| Awards / Certifications |
Title, issuer, year |
1 line / entry |
Default paper: Letter (North American audience) or A4 otherwise. No photo unless asked.
Writing rules
- One page. Tighten prose first, trim weakest bullet second, reduce leading third. Never shrink type below the design system's body minimum.
- Numbers beat adjectives. "Cut build time 40%" beats "responsible for improving build performance."
- Verbs lead bullets. Shipped, built, led, cut, grew, reduced. Drop "responsible for" entirely.
- Consistent tense. Past for past roles; present only for the current role.
- No first-person pronouns. Bullets are imperative fragments, not sentences.
- Consistent date format. Pick
Jan 2022 – Present or 2019–2022 and hold throughout.
Source & material
Résumés die from invented facts.
- Every claim (company, title, date, metric) must come from user-supplied material. No inferred metrics, ever.
- Required items present: name, contact, company, dates, ≥1 metric per senior role. If missing, produce a compact gap table and ask once.
Distill raw input
If the input is a brain dump or prior-format résumé:
- Extract every claim, number, date, name, company, tool.
- Classify into Header / Summary / Experience / Skills / Education / Awards.
- Gap-check against the Structure table.
- Ask once with a compact gap table.
Form-specific verification
Beyond done + fork_verifier_agent:
- One page at chosen paper size. Use print preview.
- Link sanity — every link has a real
href, no # stubs.
- Section consistency — bullet style, date format, and role/company order identical across entries.
- Accent discipline — accent on section headings at most, not on every bullet.
Feedback protocol
When feedback is vague, name the property, state its value, propose two options inside the design contract.
| User says |
Ask |
| "too cramped" |
Line-height is X on body, Y on bullets. Tighten section padding (Xpx → Ypx) or increase bullet line-height (Y → Z)? |
| "too loose" |
Same axes, reversed. |
| "hierarchy unclear" |
H2 is size X / weight Y. Bump H2 size, add weight contrast, or add a rule between sections? |
| "doesn't feel premium" |
Typography (font, tracking), whitespace (margin, leading), or alignment? Pick one axis. |
Never say "I'll adjust the spacing" without naming the property and new value.
When not to use
- Multi-page CV / academic curriculum vitae with publications list → long-document path.
- Résumé as a deck or interactive portfolio →
slide-deck or prototype.
- Heavily graphical / infographic résumé → typography-led; flag the mismatch and ask before producing.
1---2name: resume3description: Resume4---5# Resume67Produce a one-page CV or résumé as a single HTML document sized for A4 or US Letter.89## Structure1011Order is fixed. **Bold** = required. Any required section that would be a single bullet → merge or drop.1213| Section | Contents | Length |14|---|---|---|15| **Header** | Name, one-line role/focus, contact (email + 1–2 links), location | 2–4 lines |16| **Summary** | One or two sentences: what they do and for whom | ≤ 40 words |17| **Experience** | Reverse chronological. Per entry: role, company, location (opt), dates, 3–5 result-focused bullets | Fills the page |18| Projects | Only if Experience is thin or the role demands it | 2–4 entries |19| **Skills / Tools** | Grouped (Languages, Frameworks, Tools, …), not a wall of commas | 3–6 groups |20| Education | Degree, school, year. Relevant coursework only if junior | 1–2 lines / entry |21| Awards / Certifications | Title, issuer, year | 1 line / entry |2223Default paper: Letter (North American audience) or A4 otherwise. No photo unless asked.2425## Writing rules2627- **One page.** Tighten prose first, trim weakest bullet second, reduce leading third. Never shrink type below the design system's body minimum.28- **Numbers beat adjectives.** *"Cut build time 40%"* beats *"responsible for improving build performance."*29- **Verbs lead bullets.** Shipped, built, led, cut, grew, reduced. Drop *"responsible for"* entirely.30- **Consistent tense.** Past for past roles; present only for the current role.31- **No first-person pronouns.** Bullets are imperative fragments, not sentences.32- **Consistent date format.** Pick `Jan 2022 – Present` or `2019–2022` and hold throughout.3334## Source & material3536Résumés die from invented facts.3738- **Every claim** (company, title, date, metric) must come from user-supplied material. No inferred metrics, ever.39- **Required items present**: name, contact, company, dates, ≥1 metric per senior role. If missing, produce a compact gap table and ask once.4041## Distill raw input4243If the input is a brain dump or prior-format résumé:44451. Extract every claim, number, date, name, company, tool.462. Classify into Header / Summary / Experience / Skills / Education / Awards.473. Gap-check against the Structure table.484. Ask once with a compact gap table.4950## Form-specific verification5152Beyond `done` + `fork_verifier_agent`:5354- **One page** at chosen paper size. Use print preview.55- **Link sanity** — every link has a real `href`, no `#` stubs.56- **Section consistency** — bullet style, date format, and role/company order identical across entries.57- **Accent discipline** — accent on section headings at most, not on every bullet.5859## Feedback protocol6061When feedback is vague, name the property, state its value, propose two options inside the design contract.6263| User says | Ask |64|---|---|65| "too cramped" | Line-height is X on body, Y on bullets. Tighten section padding (Xpx → Ypx) or increase bullet line-height (Y → Z)? |66| "too loose" | Same axes, reversed. |67| "hierarchy unclear" | H2 is size X / weight Y. Bump H2 size, add weight contrast, or add a rule between sections? |68| "doesn't feel premium" | Typography (font, tracking), whitespace (margin, leading), or alignment? Pick one axis. |6970Never say *"I'll adjust the spacing"* without naming the property and new value.7172## When not to use7374- Multi-page CV / academic curriculum vitae with publications list → long-document path.75- Résumé as a deck or interactive portfolio → `slide-deck` or `prototype`.76- Heavily graphical / infographic résumé → typography-led; flag the mismatch and ask before producing.
rebyteai