frontend-bullet-writerlisted

# Frontend Bullet Writer Formula: technical action + specific tech + one real number. ## When to Use - Weak bullets: "worked on React app", "responsible for UI" - User wants stronger experience lines - `frontend-resume-scorer` handed off a **full resume rewrite** ## Rules Every bullet needs at least one of: performance (LCP, CLS, INP, bundle, TTFB, Lighthouse), scale (users, pages, teams), business (conversion, time saved), quality (coverage, a11y, bugs). If they do not have a number, ask. Allowed proxies only when they confirm: "10K+ monthly users" from analytics, "30+ pages" from the sitemap. Never invent 4.2s → 1.8s. Banned verbs: worked on, responsible for, helped with, involved in, participated in. Weave stack words only when true: React, Next.js, TypeScript, Tailwind, Vitest, Playwright, Storybook, Web Vitals, a11y, SSR. ## Patterns - Performance: route-level splitting, image/font work, LCP/INP - Features: shipped N user-facing features used by N people - Migration: class → hooks, pages → app router, CSS → tokens - Testing: 0→N coverage, e2e on a critical flow - a11y: WCAG target, axe in CI - Design system: N components, N teams adopted ## Single-bullet output ```markdown **Before:** … **After:** … **Why:** metric added / tech named / verb upgraded **Unconfirmed:** anything you still need from them ``` ## Full resume pass When the user (or the scorer skill) asks for the whole resume: 1. Keep identity, dates, employers, titles. 2. Rewrite every experience