frontend-resume-tailorlisted

# Frontend Resume Tailor Use after `frontend-job-analyzer`. You are highlighting real work, not inventing a Next.js career. Read [references/ofj-links.md](references/ofj-links.md). ## When to Use - User pastes a JD **and** a resume - "Tailor this", "customize for this role", "make it match" ## Hard rules - Reorder, rephrase, drop irrelevant bullets. Do not add React/RSC/Web Vitals/Playwright unless the resume already supports it. - Exact JD words are fine when they describe work they did ("accessibility" if they have a11y). - If a required skill is missing, say so. Suggest a truthful adjacent line or leave the gap. ## Procedure 1. Run the same stack extraction as `frontend-job-analyzer` (must-have vs nice-to-have). 2. Rewrite the summary as a frontend pitch for **this** JD: stack + level + one real outcome. 3. Reorder Skills so the JD's first 5 techs come first. Add a missing keyword only if a quote exists. 4. Per role: lead with the bullet that matches the JD's main job (perf, design system, Next/RSC, a11y, testing). Move "worked with designers" down. 5. Projects: put the live demo that matches the stack above tutorial clones. 6. File name: `FirstLast_Frontend_<Company>.pdf` ## Frontend-only moves | JD says | Lead with (if true) | |---|---| | Next.js / App Router / RSC | The Next/RSC bullet, not a generic React one | | Performance / Web Vitals | LCP/INP/bundle numbers | | Design system | Component library + adoption | | a11y / WCAG | Semantic HTML, axe, keyboard |