Writing Style Analysis Rules

Read writing samples and describe the style you observe. This is about noticing patterns and describing them in prose—not measuring or calculating anything.

Reading Writing Samples

Read Writing Samples which contains:

• Source: Which service (gmail, notion, slack)
• Context: Time period, sample count
• Samples: Array of text samples with metadata

Read through the samples to get a feel for how this person writes.

What to Observe

As you read, notice these aspects of their writing:

Tone

How does their writing feel?

• Warm and friendly, or cool and professional?
• Enthusiastic and energetic, or calm and measured?
• Direct and to-the-point, or conversational and elaborate?

Formality

What register do they use?

• Casual markers: "hey", "yeah", "thanks", contractions
• Formal markers: "please", "regarding", "sincerely", full words
• Greeting and closing patterns (if any)

Sentence Style

How do they construct sentences?

• Short and punchy, or longer and flowing?
• Simple and clear, or complex and layered?
• Consistent length, or varied?

Vocabulary

What words do they choose?

• Technical jargon or everyday language?
• Simple words or sophisticated vocabulary?
• Any distinctive phrases or expressions they repeat?

Structure

How do they organize their writing?

• Paragraphs or bullet points?
• Do they use greetings and signatures?
• How do they break up longer content?

Topics and Themes

What do they write about?

• What subjects come up repeatedly?
• What problems are they solving?
• What do they seem to care about?

Describing Style

After reading the samples, describe the style in natural prose. Write as if you're explaining to someone else how this person writes.

Good style description:

"Writes in a warm, conversational tone with short sentences. Uses casual greetings like 'Hey' and signs off with just their first name. Tends toward simple, direct language—gets to the point quickly without elaborate preambles. Often uses bullet points for lists. Writes about project updates, team coordination, and technical decisions."

Avoid:

• Percentages and statistics
• Counts and measurements
• Technical jargon about linguistics
• Vague statements without examples

Saving Style

Save the style description to Writing Style.

File structure: Each service has its own section:

• ## Gmail Style — Email writing patterns
• ## Notion Style — Document writing patterns
• ## Slack Style — Messaging patterns

Each section contains: Tone (warm and direct, professional, etc.), formality level, typical structure patterns, common greetings and signatures they use, and the topics and themes they tend to write about. Follow this with a prose description of their writing style for that platform.

When updating:

• Preserve existing service sections
• Add or update only the current service's section