Egyptian Product Copy

Purpose

Write copy that sounds chosen for its audience and task, not translated sentence by sentence. Egyptian copy is a register decision—not a license for exaggerated slang, forced humor, phonetic spellings, or indiscriminate English.

Use this skill when

Use it for Egyptian product UI, onboarding, forms, marketing, transactions, support, commerce, education, fintech-style experiences, and service businesses. If market or brand evidence is missing, state a conservative register assumption rather than inventing a persona.

Workflow

1. Identify audience, domain, relationship, risk, channel, and desired action.
2. Choose a register and record it in one sentence: for example, “professional Egyptian Arabic, warm, direct, and restrained.”
3. Create a terminology list for repeated actions, entities, and statuses before writing screens.
4. Write from user intent and consequence. Do not preserve English word order.
5. Make buttons specific, validation recoverable, and transactional content explicit about status and next steps.
6. Read the copy aloud. Remove phrases that sound theatrical, bureaucratic, patronizing, or mechanically translated.
7. Review consistency, bidi-sensitive tokens, accessibility, and factual claims in context.