// Transforms completed work into powerful resume bullet points with action verbs, technical context, and quantified impact. Use when completing tasks, updating portfolio, or preparing job applications.
| name | resume-bullet-extraction |
| description | Transforms completed work into powerful resume bullet points with action verbs, technical context, and quantified impact. Use when completing tasks, updating portfolio, or preparing job applications. |
"Your resume isn't a job description. It's a highlight reel of impact."
Transform completed work into powerful resume bullet points that demonstrate value and technical competence.
[Strong Action Verb] + [What You Did] + [Technical Context] + [Impact/Result]
| Component | Purpose | Example |
|---|---|---|
| Action Verb | Shows initiative | Engineered, Architected, Optimized |
| What You Did | The accomplishment | JWT authentication system |
| Technical Context | Shows skill | using React, Node.js, Redis |
| Impact | Why it matters | reducing auth errors by 40% |
Always try to quantify. If you can't measure directly, estimate reasonably.
[Verb] [feature] using [technologies] that [impact]
Examples:
- Engineered JWT authentication with refresh token rotation using Node.js and Redis, eliminating session hijacking vulnerabilities
- Built real-time notification system using WebSockets and React, improving user engagement by 35%
[Verb] [what] by [how], resulting in [metric]
Examples:
- Optimized database queries through index analysis and query restructuring, reducing API response time by 70%
- Accelerated page load performance by implementing code splitting and lazy loading, improving Core Web Vitals by 40%
[Verb] [problem] by [solution], preventing [impact]
Examples:
- Resolved race condition in checkout flow by implementing optimistic locking, preventing duplicate charges
- Eliminated memory leak in React components through proper cleanup, reducing crash reports by 90%
[Verb] [system] from [old] to [new], enabling [benefit]
Examples:
- Migrated monolithic application to microservices architecture using Docker and Kubernetes, enabling independent team deployments
- Refactored authentication module from session-based to JWT, reducing server memory usage by 60%
ā "Worked on the login system"
- No action verb, no specifics, no impact
ā "Responsible for user authentication"
- Passive, no accomplishment shown
ā "Helped with performance improvements"
- Vague, no ownership, no metrics
ā
"Engineered JWT authentication with refresh token rotation, reducing session vulnerability surface and supporting 50,000+ daily active users"
ā
"Optimized PostgreSQL queries through index analysis, reducing average API response time from 800ms to 120ms"
ā
"Built responsive dashboard using React and D3.js, enabling real-time visualization of 1M+ daily events"
"What's the most impressive aspect of what you just built?"
Options:
Use the formula: Verb + What + Technical Context + Impact
"Can we add numbers? How much faster? How many users? What percentage improvement?"
| Bullet Type | Resume Section |
|---|---|
| Feature/System built | Projects or Experience |
| Performance optimization | Experience (shows impact) |
| Architecture decision | Experience or Technical Skills |
| Learning/Growth | Skills or Side Projects |
Bullets are compiled in STAR story files:
ownyourcode/career/stories/[date]-[feature-name].md
The resume bullet appears at the end of each story for easy extraction.
Transforms completed work into STAR interview stories (Situation, Task, Action, Result). Use when completing tasks, preparing for behavioral interviews, or documenting achievements.
Reviews accessibility including WCAG, ARIA, keyboard navigation. Use when junior builds forms, buttons, modals, interactive elements, or asks "is this accessible", "a11y", "screen reader".
Reviews API design, REST conventions, and backend architecture. Use when junior builds API endpoints, Express routes, middleware, controllers, or asks "is this RESTful", "check my endpoint".
Reviews schema design, SQL queries, ORM patterns. Use when junior creates schema, writes queries, adds migrations, works with Prisma/MongoDB/PostgreSQL, or asks "is this SQL safe", "N+1", "index".
Guides systematic debugging through Protocol D (READ, ISOLATE, DOCS, HYPOTHESIZE, VERIFY). Use when junior says "stuck", "not working", "broken", "bug", "error", "crashed", "failing", "can't figure out", or expresses frustration. Do NOT use for general questions.
Guides documentation standards including READMEs, JSDoc, and code comments. Use when writing documentation, adding comments, or explaining code. Enforces "WHY not WHAT" principle.