Communication Style

What This File Is For

How you communicate — so that any agent producing content on your behalf sounds like you, not like a generic AI. This is the file that determines whether a draft email makes you think "that's pretty close" or "I would never say it that way." Precision matters here more than anywhere else in the portfolio. A vague communication style file is useless.

Interview Protocol

Hand this entire file to your AI build partner and say "let's do this one." Your build partner should read the instructions below and run the interview.

Instructions for the build partner: You're helping the user create their communication style file. This is the hardest file to produce well because people are bad at describing their own communication style in the abstract. Push for specifics. If they give you generalities like "I'm pretty casual," follow up with "what does casual look like — give me an example of something you'd actually write." Concrete details are everything here.

Questions to ask:

  1. When you write an email or a message, are you generally brief and to the point, or do you tend to give more context and detail?
  2. How formal is your writing at work? Does it shift depending on who you're writing to?
  3. What bothers you when you read something that was written for you or on your behalf? What makes you think "that doesn't sound like me"?
  4. Are there specific words, phrases, or patterns you know you use a lot? Things people would recognize as your voice?
  5. Are there words or phrases you actively avoid? Things that sound fake or corporate or just not you?
  6. How do you typically structure an email — do you lead with the ask, give background first, use bullet points, write in paragraphs?

When you have enough: After 5-6 questions. If the answers are vague, keep pushing for specifics before drafting. A generic file here means every agent producing content for this person will sound wrong.

After drafting: Present the draft. This is the file where the reaction pass matters most — ask the user to read each description and say whether it actually matches how they write, or whether it's aspirational.

Output Structure

# Communication Style

## Overall Style

[How you communicate in general — concise or detailed, formal or casual, direct or diplomatic. The baseline.]

## Writing Tendencies

[Sentence length, vocabulary level, use of jargon, tone. The specific texture of how you write.]

## Formatting Preferences

[How you structure emails, docs, and messages. Bullet points or paragraphs, headers or no headers, short or long.]

## What I Dislike

[AI-sounding phrases, corporate jargon, specific patterns that bother you. The things that make you rewrite a draft from scratch.]

## By Context

[How your style shifts by audience — writing to your boss vs. your team vs. a client vs. a stranger. If it doesn't shift much, say so.]

## Signature Patterns

[Words, phrases, or habits that are distinctly yours. Things people would recognize. Also words or phrases you never use.]