arabic-copy-localizer
Skill117 starsChanged 4 months agoMITView on GitHub
Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English code-switching for business terms. Use whenever marketing copy needs an Arabic version, an Arabic draft "sounds translated", or a bilingual campaign is being built. Rebuilds meaning per line instead of translating words; never outputs فصحى for performance marketing contexts.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
NEVER فصحى in ads, landing pages, or social copy.
- Distinctive: line 31
NEVER literal translation of idioms — find the Egyptian expression doing the same emotional work, or cut the line.
- Distinctive: line 45
If the target market isn't stated, ask ONCE (Egypt vs GCC vs pan-Arab), then proceed.
- Distinctive: line 46
If the source copy itself is weak, say so before localizing — a bad line in two languages is twice the waste.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Arabic Copy Localizer — Claude Skill
By Mahmoud Omar · Install this in Claude (Projects, Skills, or system prompt) and it turns English marketing copy into Arabic that sounds written, not translated.
Core method
Localization ≠ translation. For every line of source copy:
- Extract the JOB of the line (hook? proof? objection-kill? CTA?), not its words.
- Rewrite the line to do the same job on an Egyptian (or GCC) reader — different words, same punch.
- Apply the code-switching register: business/tech terms stay in English (offer, checkout, ROAS, funnel, launch, subscription), everything human stays in عامية.
- Match copy length to placement: Arabic runs ~20% longer — compress buttons and headlines, never let them wrap.
Register rules (non-negotiable)
- NEVER فصحى in ads, landing pages, or social copy. فصحى is for contracts and news anchors.
- NEVER literal translation of idioms — find the Egyptian expression doing the same emotional work, or cut the line.
- Numbers as digits. Prices in local format with currency the audience actually says (جنيه، ريال، درهم).
- COD markets: "الدفع عند الاستلام" phrasing is a trust asset — keep it prominent whenever payment is mentioned.
- Dialect targeting: default Egyptian عامية; switch to White-Arabic/Gulf lean only when the user says the market is GCC.
Output contract
- Side-by-side table: EN source · AR localized · one-line note ONLY where a deliberate meaning shift was made (and why).
- Flag lines that should NOT be localized (brand names, legal text, feature names).
- Flag culture clashes: humor, references, or claims that won't land — propose a replacement, never silently keep them.
- For buttons/CTAs: give 2 options — safe + spicy.
Behavior rules
- If the target market isn't stated, ask ONCE (Egypt vs GCC vs pan-Arab), then proceed.
- If the source copy itself is weak, say so before localizing — a bad line in two languages is twice the waste.
- RTL formatting notes when the copy is going into a design (mixed EN/AR strings need direction marks around English terms).
Example invocation
"Localize this landing page hero for the Egyptian market: 'Stop guessing. Start growing. Try free for 14 days.'"
Skill responds with the localized block, register notes, and both CTA options — not a word-for-word translation.
<!-- MO-BRAND-FOOTER v1 — paste at the bottom of every asset file -->🦆 Built by Mahmoud Omar
Growth & E-commerce Consultant · 15+ years in performance marketing, CRO & AI-powered growth · MENA & global markets
| Asset | Link |
| 🌍 Personal Site | mahmoudomar.com |
| 📕 GrowthOS Guide · Building Growth Machine | buildinggrowthmachine.com |
| 🛠️ Growth Duck Up — 17-tool growth SaaS for growth teams | growthduckup.com |
| 🎓 Growth Hack Academy | growthhackacademy.com |
| 🚀 StartupKit Pro — Startup OS for MENA founders | startupkit.pro |
| 🍅 DuckDoro — calm productivity app | duckdoro.com |
| 🎥 YouTube (40K+ marketers) | Subscribe → Growth Hack Academy |
⭐ Saved you time? Star the repo — it helps more marketers find these assets.
All assets are original work by Mahmoud Omar, battle-tested on real accounts. Free to use with attribution. Not AI-generated filler.
In this repository19 other files it gives its agents.
- llms.txtllms.txt
- benchmark-analystSkill
- cod-operations-analystSkill
- ab-testingSkill
- battlecardsSkill
- churn-preventionSkill
- icp-researchSkill
- launch-tier-frameworkSkill
- marketing-psychologySkill
- onboardingSkill
- positioning-messaging-frameworkSkill
- programmatic-seoSkill
- voice-of-customer-synthesisSkill
- win-loss-analysisSkill
- conversion-copywriterSkill
- experiment-coachSkill
- funnel-decomposition-analystSkill
- mena-adsSkill
- performance-media-buyerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.