Tone & Style Control

Beginner

The AI mirrors what you set

01 The Concept

The same facts in the wrong tone are useless. A legal memo written like a tweet. A patient diagnosis written like a journal article.

If you don't set tone, you get the model's default: bland, corporate-adjacent prose that suits nobody.

02 Weak vs. Strong

EX 01Database outage post-mortem

Write an engineering post-mortem for a database outage we had on Tuesday.

Facts:

2:47–4:12 PM PT: PostgreSQL primary became unresponsive
Root cause: a poorly-indexed query from our new analytics module triggered a table lock cascade on the orders table
Impact: 3,400 users couldn't access dashboards; API returning 503s; zero data loss
Fix: killed the offending query, promoted the read replica, analytics queries now run on the replica
Prevention: slow query logging added, read/write routing in place, index added to orders.created_at

Audience: our engineering team + CTO + VP Eng. Technical, will fact-check everything.

Tone: honest and technical — no corporate spin, no passive voice to dodge blame. Use "we" and name the root cause directly. Zero tolerance for "unexpected issues were encountered."

Format: timeline of events → root cause analysis → impact by service → fix applied → 5 specific prevention items with owner and due date.

Do NOT write: "We apologize for any inconvenience" or "unexpected behavior" or "our team worked quickly."

→ Why it works

All facts provided. Audience trust level described. Tone defined with specific anti-patterns. Banned phrases listed.

EX 02Rejection email that doesn't burn a bridge

Write a rejection email for a software engineering candidate, Marcus Webb, who interviewed for our Senior Backend Engineer role.

Context:

Marcus reached the final round (4 interviews) — a strong candidate overall
We're choosing someone with more Kubernetes experience, not because of a performance issue
Marcus was referred by someone on our team — we want to maintain the relationship
He'd be a good fit for a mid-level role if one opens in 6 months

Tone: warm and specific — not a form letter. Acknowledge the time he invested. Be honest about why without being harsh. Format: 4–5 sentences max. No bullets. First name only in the greeting. Include: one genuine observation from his interviews (leave a [SPECIFIC OBSERVATION] placeholder — I'll fill it in). Closing: an authentic door-open for future roles — only if it sounds genuine, not performative.

→ Why it works

Who the candidate is, stage reached, actual reason for rejection, relationship context.

03 Key Points

01Describe tone by analogy: 'like a senior engineer in a Slack message to the team'

02Name the emotion you want the reader to feel after reading

03List what NOT to do — as important as what to do

04Paste a writing sample and say 'match this voice'

05Separate: tone (personality), register (formal/informal), density (scannable/dense)

04 Model-Specific Notes

Claude is excellent at style matching. Paste 2–3 paragraphs you admire and say 'Match this voice in your response.' Transfer is very reliable.

05 For Your Role

Describe how you want the reader to feel. 'The reader should feel informed and in good hands, not lectured.' That sets tone better than any adjective.

Next: The Iteration Mindset →