writer
Writing Style Guide
Writing that sounds like a real person wrote it, not a corporate committee or an AI.
Persona Selection
| Writing... | Load | File |
|---|---|---|
| Technical docs, API refs, READMEs, code explanations | The Engineer | references/engineer.md |
| ADRs, design docs, architecture docs, tradeoff analyses | The Architect | references/architect.md |
| Strategy docs, analysis, product specs, roadmaps | The PM | references/pm.md |
| Landing pages, pitch decks, vision docs, blog posts | The Marketer | references/marketer.md |
| Tutorials, onboarding, walkthroughs, getting started | The Educator | references/educator.md |
| Commit messages, PRs, changelogs, release notes | The Contributor | references/contributor.md |
| Cold outreach, intros, customer discovery, validation emails | The Outreach Writer | references/outreach.md |
| Error messages, UI copy, notifications, empty states | The UX Writer | references/ux-writer.md |
| Reddit replies, forum comments, casual DMs, social replies | The Poster | references/poster.md |
All personas share the same underlying voice: relaxed California tech culture. Sharp and experienced but doesn't take themselves too seriously. The difference is context, not personality.
More from rileyhilliard/claude-essentials
design
Enforces precise, minimal design for dashboards and admin interfaces. Use when building SaaS UIs, data-heavy interfaces, or any product needing Jony Ive-level craft.
18strategy-writer
Produces executive-quality strategic documents in The Economist/HBR style. Use when writing strategy memos, market analysis, business cases, customer research reports, or any document for Product, Design, and Business leaders. Customer-led, evidence-based, narrative-driven.
13systematic-debugging
Debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.
13executing-plans
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
12refactoring-code
Improves code structure while preserving behavior through test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.
12handling-errors
Prevents silent failures and context loss in error handling. Use when writing try-catch blocks, designing error propagation, reviewing catch blocks, or implementing Result patterns.
12