Egyptian Product UX

Purpose

Turn local context into testable product decisions without treating Egyptians as one homogeneous persona. Separate three layers in every recommendation:

1. Universal UX: accessibility, feedback, error recovery, clear hierarchy.
2. Arabic-wide: RTL, mixed scripts, Arabic typography.
3. Egypt-specific: phone/address patterns, EGP display, locally validated channels and expectations.

Start from the dated defaults in references/egypt-facts.md: phone formats, address structure, EGP display, digits, time zone and weekend, common payment methods, and messaging channels. Design with those directly. Only facts marked (changes) there, plus anything legal or provider-specific, need confirmation from a current official source before they become hard rules.

Use this skill when

Use it to design or review acquisition, onboarding, registration, checkout, booking, marketplace, education, SaaS, support, and identity/document flows for Egypt.

This skill owns the user-facing flow. Neighboring skills own the rest, so load them when the task reaches their layer: