CommunityWriting & Editinggithub.com

arabic-copywriting

Writes and reviews clear Modern Standard Arabic (MSA) product and UI copy - buttons, errors, onboarding, emails, landing pages - with one language per page, no machine-translation tells, a consistent glossary, correct Arabic punctuation and digits, and a tone that fits Saudi and Gulf audiences. Use when translating an English interface into Arabic, writing Arabic microcopy from scratch, reviewing Arabic text that "sounds translated", building an Arabic glossary, or when the user says «صياغة عربية»، «ترجمة الواجهة»، «النص يبدو مترجمًا»، «راجع النصوص العربية»، «كتابة محتوى عربي».

What is arabic-copywriting?

arabic-copywriting is a Claude Code agent skill that writes and reviews clear Modern Standard Arabic (MSA) product and UI copy - buttons, errors, onboarding, emails, landing pages - with one language per page, no machine-translation tells, a consistent glossary, correct Arabic punctuation and digits, and a tone that fits Saudi and Gulf audiences. Use when translating an English interface into Arabic, writing Arabic microcopy from scratch, reviewing Arabic text that "sounds translated", building an Arabic glossary, or when the user says «صياغة عربية»، «ترجمة الواجهة»، «النص يبدو مترجمًا»، «راجع النصوص العربية»، «كتابة محتوى عربي».

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/MahsumahCloud/saudi-claude-skills/tree/HEAD/skills/arabic-copywriting

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Arabic Copywriting for Products

Arabic version: SKILL.ar.md. Answer in the language the user writes in.

Good Arabic product copy reads as if it had been written in Arabic first. Most Arabic interfaces fail in a few predictable ways. They translate English sentence structure word by word, they lean on passive filler («يتم»، «من خلال»), they mix English labels into Arabic screens, and they use different words for the same thing on different screens. This skill gives a method to write and review copy that avoids those problems.

When to use

  • Translating or adapting an English UI, email or landing page into Arabic.
  • Writing new Arabic microcopy: buttons, labels, empty states, errors, confirmations, notifications.
  • Reviewing Arabic text that users or stakeholders say "feels translated" or "feels cold".
  • Creating or enforcing a product glossary across web, mobile, emails and support articles.

When NOT to use

  • Layout, direction and number rendering problems. Use arabic-rtl-ui.
  • Legal texts (terms, privacy policy) that need a lawyer's review. You may improve readability, but flag that legal meaning must be confirmed by counsel.
  • Dialect marketing (Saudi colloquial ads). This skill targets MSA. If the brand voice asks for dialect, say so explicitly and keep transactional screens in MSA.

Method

  1. Fix the language of the page. One page, one language. An Arabic page has Arabic labels, Arabic buttons and Arabic errors. Keep only brand and product names in their original script (for example «Visa», «Apple Pay»), and only when the brand does not have an official Arabic name.
  2. Collect context before writing. Who reads this (consumer or business, first-time or expert), where it appears (button, toast, email subject), how much space there is, and what the user should do next.
  3. Load or build the glossary. Reuse the product's existing terms. If none exists, start from the starter glossary below and record every new decision.
  4. Write the meaning, not the English words. Read the English, close it, and write how an Arabic writer would say it. Then compare with the English to check that no information was lost.
  5. Remove machine-translation tells (list below). Prefer active verbs, short sentences and natural Arabic word order (verb before subject is often more natural in MSA).
  6. Apply Arabic punctuation and the product's digit policy.
  7. Match the tone to the moment: calm and specific for errors, warm and short for success, clear and neutral for payments and legal.
  8. Check fit. Arabic strings can be longer or shorter than English. Do not assume a ratio. Test in the real component, in both directions, on a small phone width.
  9. Review with the output table (format below) and hand over the final strings with their keys.

Machine-translation tells and fixes

TellWhy it reads badlyFix
«قم بالنقر على...»، «قم بإدخال...»Calque of "Please click". The extra verb adds nothing.«انقر...»، «أدخل...»
«يتم حفظ التغييرات»Passive «يتم + verbal noun» hides the actor and is heavy«حُفظت التغييرات» or «حفظنا التغييرات»
«بواسطة»، «من خلال» used for every "by/through"Filler copied from English prepositionsUse the verb directly: «سجّل الدخول بحساب Google»، «ادفع بالبطاقة»
«هل أنت متأكد أنك تريد حذف هذا العنصر؟»Long English structure«حذف العنصر؟ لا يمكن التراجع عن ذلك.»
Wrong gender or number agreement: «الملفات تم رفعه»Machine output ignores agreement«رُفعت الملفات»
English word order: «الإعدادات الخاصة بالحساب»"Account's settings" pattern«إعدادات الحساب» (construct state, إضافة)
Title Case or ALL-CAPS emphasis carried overArabic has no capitals. Emphasis is lost or replaced by odd bolding.Use word choice, placement, or weight in the design
«عزيزي المستخدم» in every messageDistant and template-likeAddress the person directly, or drop the salutation in UI
Literal idioms: «اضرب الأرض جاريًا»Nonsense in ArabicRewrite the intent: «ابدأ فورًا»
«الرجاء» repeated in every instructionOver-polite fillerUse it once where a real request is made, or not at all

Starter glossary (EN → AR)

EnglishArabicNote
Sign in / Log inتسجيل الدخولButton: «سجّل الدخول»
Sign outتسجيل الخروج
Sign up / Create accountإنشاء حسابAvoid «التسجيل» alone (ambiguous)
Accountالحساب
Profileالملف الشخصي
Settingsالإعدادات
Dashboardلوحة التحكم
Homeالرئيسية
SaveحفظButton verb: «احفظ» or noun «حفظ», pick one style
Cancelإلغاء
Deleteحذف
Editتعديل
Uploadرفع
Downloadتنزيل
SearchبحثPlaceholder: «ابحث...»
Filterتصفية
Sortترتيب
Notificationsالإشعارات
Billingالفوترة
Invoiceفاتورة
Payment methodوسيلة الدفع
Subscriptionاشتراك
PlanالباقةKeep one word. Do not alternate with «الخطة»
Free trialتجربة مجانية
Upgradeترقية
Passwordكلمة المرور
Forgot password?نسيت كلمة المرور؟
Two-factor authenticationالتحقق بخطوتين
Verification codeرمز التحقق
Emailالبريد الإلكتروني
Mobile numberرقم الجوالSaudi usage. «الهاتف المحمول» is wider-Arab
Errorخطأ
Warningتنبيه
Successتم بنجاحPrefer a specific sentence instead
Loading...جارٍ التحميل...Not «جاري» without context; «جارٍ» is correct MSA
SubmitإرسالPrefer the specific action: «أرسل الطلب»
Continue / Nextمتابعة / التالي
Backرجوع
Helpالمساعدة
Supportالدعم
Terms of serviceالشروط والأحكام
Privacy policyسياسة الخصوصية

The glossary is a starting point, not a standard. Once the product picks a term, use it everywhere: UI, emails, help centre, support replies.

Punctuation

  • Arabic comma «،», semicolon «؛» and question mark «؟». Do not use the Latin , ; ? inside Arabic sentences.
  • No space before punctuation, one space after: «الاسم، البريد، الجوال».
  • Quotation marks: «...» (guillemets). Be consistent per product.
  • The full stop is the Latin .. Inside a short button or label, omit it.
  • Do not use the Latin , as a thousands separator in Arabic prose when digits are Arabic-Indic. Let Intl.NumberFormat handle grouping.
  • Avoid the elongation character «ـ» (tatweel) for justification or decoration in UI text. It breaks search and copy-paste.

Numbers, currency and dates

  • Pick Western digits (0-9) or Arabic-Indic digits (٠-٩) for the whole product, write it in the style guide, and do not mix them on one screen.
  • Currency: «ر.س» (abbreviation) or «ريال» (word). Pick one style for UI and one for prose. Place the amount and symbol in the order the formatter produces for the locale, and do not hand-assemble it.
  • Number and noun agreement (العدد والمعدود) is hard to get right with variables. Prefer phrasing that avoids it: «عدد الملفات: 3» instead of «3 ملفات» when the number is dynamic. Or use ICU plural rules (zero, one, two, few, many, other all exist for Arabic).
  • Dates: decide whether to show Hijri, Gregorian or both, and say which calendar is shown. See hijri-dates.

Tone for Saudi and Gulf audiences

  • Respectful, direct and brief. Prefer «أدخل رقم الجوال» over flowery openings.
  • MSA by default. Light familiarity is fine in marketing if the brand voice allows it. Payments, security, errors and legal stay in clear MSA.
  • Address form: second person singular masculine imperatives («أدخل»، «اختر») are the common default in Arabic UI. If the product wants wording that reads well for everyone, lean on forms that look the same for both genders when unvocalised («يمكنك تعديل البيانات لاحقًا»), first person plural from the product («سنرسل لك الرمز»), or noun phrases («إدخال الرمز مطلوب»). Use plural imperatives («أدخلوا») only if the brand chose that voice. Decide once and record it.
  • Avoid religious phrases in transactional UI unless the context calls for them (for example a seasonal greeting chosen by the brand). Never put them in error or payment messages.
  • Avoid humour in errors, loss of data or payment failures.

Buttons, errors, confirmations

  • Buttons: an imperative verb that names the outcome: «احفظ التغييرات»، «ادفع 99 ر.س»، «أنشئ الحساب». Avoid «موافق» when a specific verb exists.
  • Errors: what happened, then what to do. «تعذّر حفظ الملف لأن حجمه أكبر من 10 ميجابايت. اختر ملفًا أصغر.» Never blame the user («أدخلت بيانات خاطئة»), and never show raw codes alone.
  • Confirmations of destructive actions: name the object and the consequence. «حذف الفاتورة INV-204؟ لا يمكن استرجاعها بعد الحذف.» Buttons: «احذف الفاتورة» / «إلغاء».
  • Empty states: say what will appear here and how to start. «لا توجد فواتير بعد. ستظهر هنا فواتيرك بعد أول عملية دفع.»

Checklist

  • Page is fully Arabic: no English labels, buttons or errors (brand names excepted).
  • Every term matches the glossary. No synonyms for the same concept.
  • No «قم بـ», no unnecessary «يتم», «بواسطة», «من خلال», «الخاص بـ».
  • Gender and number agreement checked, including around variables.
  • Arabic punctuation «، ؛ ؟ « »», no space before marks.
  • One digit system across the product. Currency written one consistent way.
  • Buttons are verbs naming the outcome.
  • Errors say what happened and what to do, without blame.
  • Tone fits the moment (payment and security in neutral MSA).
  • Strings tested in the real component for overflow and wrapping.
  • Dynamic strings use ICU plurals or avoid number-noun agreement.

Do / Don't

DoDon't
Write from the meaning, then check against the EnglishTranslate word by word
«انقر»، «أدخل»، «اختر»«قم بالنقر»، «قم بإدخال»، «قم باختيار»
«حُفظت التغييرات»«تم القيام بحفظ التغييرات»
«إعدادات الحساب»«الإعدادات الخاصة بالحساب»
Keep one term per conceptAlternate «الباقة» / «الخطة» / «الاشتراك» for the same thing
Use «، ؛ ؟»Use , ; ? in Arabic sentences
Translate every label on an Arabic pageLeave "Dashboard", "Settings", "Submit" in English
Name the action on buttons«موافق» / «إرسال» everywhere

Examples

  1. Button
    • Before: «قم بالضغط هنا لإتمام عملية الدفع»
    • After: «ادفع الآن»
  2. Success toast
    • Before: «لقد تم حفظ الإعدادات الخاصة بك بنجاح!»
    • After: «حُفظت الإعدادات.»
  3. Error
    • Before: «خطأ: إدخال غير صالح.»
    • After: «رقم الجوال غير مكتمل. اكتب 10 أرقام تبدأ بـ 05.»
  4. Mixed language
    • Before: «اذهب إلى Settings ثم اضغط Save.»
    • After: «افتح الإعدادات، ثم اختر «حفظ».»
  5. Passive chain
    • Before: «سيتم إرسال رمز التحقق إليك من خلال رسالة نصية بواسطة النظام.»
    • After: «سنرسل لك رمز التحقق برسالة نصية.»
  6. Destructive confirmation
    • Before: «هل أنت متأكد من أنك تريد أن تقوم بحذف هذا الحساب؟ نعم / لا»
    • After: «حذف الحساب نهائيًا؟ ستُحذف بياناتك ولا يمكن استرجاعها.» Buttons: «احذف الحساب» / «إلغاء»
  7. Empty state
    • Before: «لا يوجد بيانات لعرضها.»
    • After: «لا توجد طلبات بعد. أنشئ أول طلب ليظهر هنا.»
  8. Agreement with a variable
    • Before: "لديك " + n + " رسالة جديدة"
    • After: ICU message {n, plural, zero {لا رسائل جديدة} one {رسالة جديدة واحدة} two {رسالتان جديدتان} few {# رسائل جديدة} many {# رسالة جديدة} other {# رسالة جديدة}}

Review output format

When reviewing copy, return a table and nothing vague:

#OriginalIssueSuggested
1قم بإدخال كلمة المرورCalque «قم بـ»أدخل كلمة المرور
2الاعداداتMissing hamza (إ)الإعدادات
3SubmitEnglish on an Arabic pageأرسل الطلب

After the table, list any new glossary decisions and open questions (for example "Is the product voice singular masculine or plural?").

References

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

Related Skills