Review and update documents to comply with Evan Curtin's professional writing style. Use when editing resumes, bios, LinkedIn content, blog posts, or any professional writing that should reflect Evan's voice and principles.
Review and update documents to match the voice and standards defined in style_guide.md.
Copy and complete this checklist:
Style Review:
- [ ] No hype or performative language
- [ ] Outcomes before activities
- [ ] Systems, not tasks
- [ ] Concrete verbs (built, shipped, designed, reduced)
- [ ] Scale/context included where relevant
- [ ] Honest about challenges
- [ ] Every sentence earns its place
- [ ] Sounds like Evan, not a marketing department
| Avoid | Why |
|---|---|
| "Spearheaded", "leveraged", "synergized" | Inflated verbs |
| "Thought leader", "visionary" | Hype language |
| "Passionate about..." | Performative |
| "This is the correct way" | Performative absolutism |
| Activity lists without outcomes | Missing impact |
| Vague claims without scale/context | Unearned confidence |
Before (activity-focused):
Worked on fraud detection systems and helped improve performance.
After (outcome-focused):
Built daily-refit fraud detection systems processing >1TB/day; prevented ~$14M in annual fraud losses.
Before (hype):
Passionate thought leader driving transformative AI initiatives across the enterprise.
After (grounded):
Build production ML systems; focus on evaluation, reliability, and real-world impact.
The canonical style guide is at style_guide.md in the project root. If this skill conflicts with that document, the style guide takes precedence.