Egyptian Web Audit

Purpose

Produce evidence-backed findings about whether a product works and feels intentional for Egyptian users. Do not equate the presence of Arabic with localization quality. Do not assign a numerical score unless the user explicitly requests one and defines how it will be used.

Use this skill when

Use it to audit an existing site, app, page set, design, or implementation for Egypt. Load specialist skills when deeper analysis is needed: arabic-ui, arabic-rtl, egyptian-copy, egyptian-product-ux, and egyptian-backend for observable integration/data issues.

Workflow

1. Agree or infer the mode, scope, environment, target audience, supported locales, and critical journeys. State access limits.
2. Collect evidence at representative phone and desktop widths. Exercise interaction rather than judging screenshots alone.
3. Trace at least one critical journey end to end, including error and recovery paths when safe.
4. Record findings with reproducible evidence and separate observed behavior from inference.
5. Deduplicate root causes. One broken direction provider may explain many component symptoms.
6. Prioritize by user harm and journey impact, then propose a concrete fix and example.
7. Finish with systemic patterns, quick wins, and unknowns requiring product, legal, operational, or technical confirmation.