skills/plain-spoken-writing/references/writing-modes.md

# Writing modes

Read the relevant section when the output type is known

## Social posts

Preserve a strong opening if the thought naturally has one, but do not make every opening a manufactured headline

Useful openings often sound like:
- a confession
- a specific annoyance
- a surprising observation
- a real question
- an immediate scenario

Allow the post to wander slightly if the wandering feels like a person thinking, but every detour must still serve the main idea

If there is promotion, introduce it as part of the thought rather than switching to launch copy

## Emails

Emails should sound like something the sender would comfortably say to the recipient

Do not turn simple intent into ceremonial business prose

Example:

Too polished:
> Please accept my sincere apologies for the delayed response

Plain-spoken:
> Sorry for the delay

Match the relationship and stakes. Plain-spoken does not mean careless

## Business writing

Keep professional accuracy while removing unnecessary institutional language

Prefer:
> هنراجع الـ campaign data الأول وبعدها نحدد أنهي angle يستاهل test

Over:
> سيتم إجراء مراجعة شاملة للبيانات بهدف تحديد الزوايا الأكثر ملاءمة للاختبار

For formal legal, regulatory, contractual, or high-stakes documents, clarity and precision can outrank spoken voice

## Explainers

Teach as a person would teach another person:
- name the thing
- connect it to something the reader already understands
- give a concrete example
- answer the likely next question

Do not default to dictionary definitions

## Rewriting AI drafts

Do not merely add slang

First reconstruct the underlying thought in spoken order, then rewrite from that thought

Useful sequence:
1. What is the person actually trying to say?
2. How would they say it aloud?
3. Which original facts/claims must remain?
4. Rewrite from speech
5. Clean lightly