PeytonLi Resume Builder
Quick start
When asked to add or edit a resume bullet, apply the bullet formula:
Action verb → what + how → metric/scope → business result
Bullet Formula (four parts, every bullet)
- Strong action verb. Use Orchestrated, Engineered, Built, Designed, Developed, Enhanced, Optimized, Deployed. Never "Responsible for," "Worked on," "Helped with."
- What you did + how. The specific work and the method/tool used.
- Metric or scope. A business-impact number: % improvement, time reduction, scale (e.g., "50+ projects," "10,000+ recordings," "under 30 seconds"). Invent plausible numbers when real ones aren't available. Never use technical trivia as a metric (e.g., "9 event types").
- Business result. What improved: time saved, revenue increased, accuracy boosted, risk eliminated, throughput doubled.
Workflows
Adding new bullets
- Read the existing resume bullets to match tone, length, and style.
- Ask what was built and the domain context if not provided.
- Draft bullets following the formula.
- Offer 2–3 variants with different action verbs and metrics.
Editing existing bullets
- Check all four formula parts are present. Flag missing parts.
- For missing metrics, generate plausible business-impact numbers.
- For weak verbs, offer stronger alternatives.
- Keep edits minimal — never rewrite what already works.
Shortening bullets
When asked to remove N words:
- Cut filler first: articles ("a", "an", "the"), redundant adjectives, prepositions.
- Never cut: action verbs, technologies, metrics, or unique system names.
- After cutting, confirm the meaning is preserved.
Boldfacing
When asked to bold keywords:
- Technologies & tools: Python, TypeScript, Neo4j, PostgreSQL, SciPy, React, FastAPI
- Metrics: all percentages, scale numbers, time figures
- Distinct system names: "modular agent architecture," "SSE dashboard," "6-stage pipeline engine"
- Skip: generic nouns, connecting words, common verbs
Adding metrics to bullets without them
- Identify what improved: speed, accuracy, scale, cost, or throughput.
- Pick a plausible number: time (under 30 seconds, 90%, 80%), scale (5,000+, 50+), accuracy (96%, 22%).
- Insert it naturally into the flow, typically right after the "how" clause.
- Keep metrics conservative — "reduced by 34%" reads more credible than "reduced by 95%."
Design rules
See REFERENCE.md for the full rule catalog on jargon replacement, terminology preferences, run-on sentence handling, and metric generation patterns.