نوشتن فارسی محاوره‌ای

---
name: persian-conversational
description: >-
  Write natural colloquial Persian (محاوره‌نویسی) as Persian speakers actually
  write in chats, social media, consumer products, onboarding, notifications,
  and friendly support. Use when the user asks for فارسی محاوره‌ای، خودمونی،
  عامیانه، لحن دوستانه، کپشن، استوری، پیام چت, or casual Persian product copy.
  Do not use for legal, academic, administrative, contractual, or explicitly
  formal writing; use persian-formal or persian-writing when appropriate.
---

# Conversational Persian (فارسی محاوره‌ای)

Write Persian in a natural spoken register without making it sloppy, childish, exaggerated, or artificially slang-heavy.

The goal is not to mechanically convert formal Persian into colloquial Persian. Rewrite the sentence as a Persian speaker would naturally say or type it in the target context.

Always determine the appropriate level of informality before writing.

## 1. Choose the register

Colloquial Persian is not a single tone. Choose the appropriate level based on where the text will be used.

| Level | Typical use                                                          | Style                                                      |
| ----- | -------------------------------------------------------------------- | ---------------------------------------------------------- |
| Light | Product UI, onboarding, landing pages, newsletters, customer support | Natural spoken grammar with controlled informality         |
| Full  | Chats, DMs, Telegram, Instagram, stories, casual social posts        | More relaxed vocabulary, contractions, and spoken phrasing |

### Default behavior

If the user only says "make it casual":

* Use **Light** for product and professional contexts.
* Use **Full** for personal chats and social media.
* If the context is unclear, prefer **Light**.

Do not make professional product copy sound like a private chat unless explicitly requested.

---

## 2. Rewrite naturally, do not translate mechanically

Do not apply word-for-word substitutions from formal Persian.

Instead, reconsider:

* sentence structure
* vocabulary
* verb forms
* pronouns
* particles
* sentence length
* rhythm
* level of familiarity

Avoid Persian that sounds translated, literary, bureaucratic, or generated.

### Example

Avoid:

> در صورت تمایل می‌توانید درخواست خود را ارسال نمایید.

Prefer:

> اگه خواستید، درخواستتون رو بفرستید.

For a more neutral product tone:

> می‌تونید درخواستتون رو بفرستید.

---

## 3. Spoken verb forms

Use natural spoken forms when the context calls for them.

| Formal               | Colloquial         |
| -------------------- | ------------------ |
| است                  | ـه                 |
| هستند / نیستند       | هستن / نیستن       |
| می‌شود / نمی‌شود     | میشه / نمیشه       |
| می‌خواهم / می‌خواهی  | می‌خوام / می‌خوای  |
| می‌توانم / می‌توانید | می‌تونم / می‌تونید |
| می‌روم / می‌رود      | میرم / میره        |
| می‌گویم / می‌گوید    | میگم / میگه        |
| می‌دهم / می‌دهد      | میدم / میده        |
| می‌آید / می‌آیند     | میاد / میان        |
| بگذار / بگذارید      | بذار / بذارید      |

Do not force spoken forms when they make the text unnatural for the context.

For example, professional customer-facing copy may naturally use:

> می‌تونید ادامه بدید.

rather than an exaggeratedly casual:

> می‌تونی ادامه بدی.

---

## 4. Pronouns and politeness

Choose `تو` or `شما` deliberately and keep it consistent.

### Default

For customers, users, followers, and people the brand does not know personally:

> شما

with natural spoken verbs:

> می‌تونید ببینید.
> می‌خواید ادامه بدید؟
> اطلاعاتتون رو وارد کنید.

Use `تو` when:

* the product already has a clearly informal voice
* the user explicitly asks for it
* the context is clearly personal or familiar

Do not mix `تو` and `شما` in the same artifact unless the context requires it.

Avoid excessive formality inside a colloquial text:

> جناب‌عالی می‌توانید ملاحظه بفرمایید.

---

## 5. Colloquial vocabulary

Use common spoken vocabulary when appropriate.

Examples:

| Formal         | Natural colloquial |
| -------------- | ------------------ |
| اکنون          | الان               |
| در صورتی که    | اگه                |
| می‌خواهم       | می‌خوام            |
| می‌توانم       | می‌تونم            |
| امکان‌پذیر است | می‌شه              |
| انتخاب نمایید  | انتخاب کنید        |
| ارسال نمایید   | بفرستید            |
| برای من        | برام               |
| برای شما       | براتون             |

Do not convert every word simply because it has a colloquial alternative.

Words such as these can remain unchanged when they sound natural:

> تنظیمات
> حساب کاربری
> اطلاعات
> پرداخت
> امنیت
> اعلان
> سفارش

The goal is natural Persian, not maximum informality.

---

## 6. Common spoken sound changes

Use common spoken forms when appropriate, especially in Full colloquial text.

Examples:

> خانه → خونه
> نان → نون
> دندان → دندون
> زمان → زمون

Do not blindly apply these transformations.

Keep:

* proper nouns
* names
* brands
* technical terms
* established terminology

unchanged unless a conventional spoken form clearly exists.

For example:

> ایران
> FarsiUI
> React
> GitHub

should not be altered merely to make them sound more colloquial.

---

## 7. Spoken particles

Particles can make conversational Persian feel natural, but they should be used selectively.

Useful particles include:

> خب، حالا، دیگه، یعنی، راستش، ببین، که، ها، مگه

Examples:

> خب، از اینجا شروع کنیم.

> گفتم که مشکلی نیست.

> یادت نره ها.

> مگه میشه؟

Do not add particles to every sentence. Overuse makes the text sound artificial.

---

## 8. Reactions and conversational expressions

For chats and social content, short reactions are often more natural than complete formal sentences.

Examples:

> جدی؟
> عالیه!
> دمت گرم.
> وای.
> خب بریم.
> آره، دقیقاً.
> حله.

Use slang according to the context.

Everyday casual words are generally safe:

> عالیه، کلی، یه عالمه، حله، بازم

Stronger slang such as:

> داش، خفن، ترکوندی

should only be used when the requested voice or existing brand voice clearly supports it.

Do not invent slang to make text appear human.

---

## 9. ZWNJ and Persian orthography

Colloquial writing still needs correct Persian typography.

Use Persian characters:

* `ی` (U+06CC), not `ي`
* `ک` (U+06A9), not `ك`

Use ZWNJ where standard Persian orthography requires it:

> می‌خوام
> نمی‌تونم
> بچه‌ها
> خونه‌مون
> راه‌اندازی

Do not insert ZWNJ mechanically into every word. Follow normal Persian orthographic conventions.

---

## 10. The هکسره problem

Be careful with the colloquial `ـه` ending and ezafe.

Compare:

> این ماشینه.
> ماشینِ علی.

In the first sentence, `ـه` means `است`:

> این ماشین است.

In the second, `ـِ` is ezafe:

> ماشینِ علی

### Practical test

When unsure whether `ـه` is the colloquial form of `است`, mentally replace it with `است`.

If the sentence still works, `ـه` may be correct.

If the phrase expresses a relationship between two nouns/adjectives, check whether ezafe is required instead.

Never produce forms such as:

> ماشینه علی

when the intended meaning is:

> ماشینِ علی

---

## 11. Persian numbers

Use Persian digits in normal Persian prose when appropriate:

> ۳ تا سفارش
> ساعت ۱۰
> ۲ روز دیگه

Preserve Latin digits in:

* code
* URLs
* version numbers
* IDs
* file names
* technical identifiers
* API values

Do not modify user-provided technical values.

---

## 12. Punctuation

Use natural Persian punctuation:

> ،
> ؟
> ؛
> « »

Avoid spacing mistakes:

> درست: اگه آماده‌ای، شروع کنیم.
> نادرست: اگه آماده‌ای ، شروع کنیم .

Do not add excessive punctuation:

> عالیییییی!!! 😍🔥🔥🔥

unless the requested voice explicitly calls for that style.

### Dashes

Do not introduce em dashes as a default stylistic habit.

Prefer normal Persian sentence structure and punctuation. If a dash is already present in user-provided text or is genuinely appropriate to the requested style, do not remove it mechanically.

---

## 13. Persian-English text

Preserve technical names, product names, APIs, libraries, and code exactly.

Examples:

> React
> Next.js
> GitHub
> FarsiUI
> API
> MCP

Do not translate or Persianize technical identifiers unless the user explicitly asks for localization.

When Persian and English appear together, prioritize readable RTL/LTR ordering and do not corrupt technical strings.

---

## 14. UI copy

Conversational UI copy should be friendly without becoming chatty.

Prefer:

> اطلاعاتتون رو وارد کنید.

over:

> خب، حالا اطلاعاتتون رو وارد کنید تا بریم مرحله بعد!

unless the product voice explicitly calls for that tone.

Buttons should usually be short:

> ادامه
> ذخیره
> دوباره تلاش کنید
> ارسال کد
> مشاهده جزئیات

Do not turn every UI label into a conversational sentence.

---

## 15. Notifications and errors

Keep the message human and useful.

Avoid:

> کاربر گرامی، متأسفانه عملیات مورد نظر شما با خطا مواجه گردید.

Prefer:

> پرداخت انجام نشد. دوباره امتحان کنید.

For friendly contexts:

> پرداخت انجام نشد. یه بار دیگه امتحان کنید.

Prefer clarity over forced informality.

---

## 16. Social and chat writing

For social media and chats:

* Keep sentences short when appropriate.
* Use natural contractions.
* Allow incomplete sentences when they feel natural.
* Do not over-explain.
* Do not add unnecessary introductions or conclusions.
* Match the user's existing tone.
* Preserve intentional slang and humor when rewriting.
* Do not make every sentence perfectly polished if the requested style is genuinely casual.

A natural chat message may be:

> آره، دیدمش.
> یه کم خلوت‌تر بشم حتماً نگاهش می‌کنم.

It does not need to sound like edited marketing copy.

---

## 17. Avoid common AI patterns

Avoid generic phrases that make Persian writing feel generated or overly polished.

Do not automatically use:

> در دنیای امروز...

> نه تنها ... بلکه ...

> امیدوارم مفید بوده باشه.

Avoid artificial three-part lists such as:

> سریع، آسان و مطمئن

unless the content genuinely requires that structure.

Avoid:

* unnecessary emojis
* excessive exclamation marks
* repeated filler
* generic motivational phrases
* unnatural politeness
* unnecessary English words
* literal translations from English
* overly literary vocabulary in casual contexts

Do not remove a phrase merely because it resembles an AI pattern if it is genuinely appropriate to the context.

---

## 18. Preserve the user's voice

When rewriting user-provided Persian:

1. Preserve the intended meaning.
2. Preserve the user's personality.
3. Preserve intentional slang.
4. Fix unnatural wording only when necessary.
5. Do not make the text more formal unless requested.
6. Do not make it more casual than requested.
7. Do not replace simple natural wording with sophisticated alternatives just for variety.

If the user's original text is already natural, make minimal changes.

---

## 19. Context-specific defaults

### Consumer product

Prefer:

> خوش اومدید! برای شروع، پروفایل‌تون رو کامل کنید.

### Friendly support

Prefer:

> سلام، ببخشید که معطل شدید. اگه هنوز کد نرسیده، روی «ارسال دوباره» بزنید.

### Chat

Prefer:

> آره، دیدمش. یه کم خلوت‌تر بشم حتماً نگاهش می‌کنم.

### Social media

Prefer short, natural sentences with the user's actual tone rather than polished marketing language.

---

## 20. Before returning the text

Check the final output:

* Is the register clearly Light or Full?
* Is the register consistent from beginning to end?
* Does the text sound naturally Persian when read aloud?
* Are formal verbs leaking into a colloquial context?
* Is `تو` / `شما` consistent?
* Is ZWNJ used according to normal Persian typography?
* Are `ی` and `ک` Persian characters?
* Are Persian punctuation marks used correctly?
* Are technical names and code preserved?
* Is slang appropriate for the context?
* Did the rewrite preserve the user's meaning and personality?
* Did the text become unnecessarily casual, polished, or verbose?
* Does anything sound like a literal translation or AI-generated Persian?

### Final rule

When choosing between a technically correct sentence and a sentence that a Persian speaker would naturally write, prefer the natural sentence **as long as the meaning remains accurate and the context allows it**.