| name | recruiter-scan-edit |
| description | Edit portfolio content so recruiters and hiring managers can understand the strongest proof within 30 seconds. Use for top-level pages, README, summaries, card summaries, and project highlights. |
| paths | ["README.md","portfolio-config.json","src/content/**/*.md","src/pages/**/*.astro","src/data/**/*.ts"] |
Purpose
Make portfolio content faster to scan without flattening the nuance.
Editing priorities
- Put the strongest proof first.
- Prefer concrete scope over abstract adjectives.
- Make role fit obvious.
- Keep sentences shorter.
- Use bullets for proof points.
- Remove repeated phrasing.
- Replace internal jargon with portable language.
Preferred phrases
Use where accurate:
- technical program leadership
- product operations
- operational systems
- roadmap ownership
- requirements quality
- release planning
- stakeholder alignment
- workflow automation
- governance systems
- staff-adopted tooling
- production-used workflows
- field-tested operating model
- privacy-conscious analytics
- cross-functional delivery
Avoid overusing
- messy work
- people can actually use
- practical
- operating layer
- clearer
- systems
- helped with
- passionate
Output expectations
When editing, produce direct replacement text.
When reviewing, identify:
- what to keep
- what to cut
- what to move higher
- what to quantify
