writing

Rewrite bloated, hedged, or AI-sounding prose into this owner's plain-language house style. Use when a draft is wordy or padded, leans on passive voice and nominalizations, hedges, uses Title Case headings, or scatters bold and italics through paragraphs for emphasis, and when the user says "tighten this", "make it readable", "clean up the prose", "too wordy", "plain English", "plain language", or "house style". Applies the house rules: active voice, front-loaded content, sentence case, no bold or italics for emphasis, no em dashes. For reports, research write-ups, guidance, documentation, and summaries.

Answer with a compact visual instead of a wall of prose: pseudocode, a call tree, a component tree, a shallow file tree, a types-and-signatures sketch, a diff of any of those, a mermaid diagram, or one focused HTML page. Use when the user says "show me", "draw this", "diagram it", "what does this look like", "I can't follow that", or when a plain-text answer would be a long paragraph about structure. Reach for it unprompted while designing before code exists (the shape of the types, signatures, and call stacks) and while reading a large diff. For chart and dashboard design use dataviz; for diagram craft inside a published page use artifact-diagramming; to fix the register of prose that stays prose, use plain-language-us.

Reproduce this specific user's writing voice from evidence: their phrasing in the current conversation, supplemented by a saved voice profile stored in their Claude config directory. Use when drafting anything that will go out under the user's name — an email or reply, a GitHub issue comment, a Slack message, a release announcement, a README intro, a standup note — and when they say "in my voice", "sound like me", "in my style", "match my tone", "the way I'd write it", or "don't make it sound AI-generated". Drafting from generic instinct produces exactly the flat register they are trying to avoid; the conversation and the profile carry the specific rhythm, vocabulary, and habits that make a draft read as theirs.

Rewrite the last message when it did not land: re-pitched with more context, in plainer terms, using the project's own vocabulary for things.