Mood and tone before the first screen
Before tokens or AI, there is a direction the client and I pick by hand. How I get there.
When the app reads right to left
Adding a right-to-left language like Arabic is not the same as flipping the file. What mirrors, what never should, and who has to check it.
Arabic and Hebrew read right to left, RTL for short. The tempting shortcut is to duplicate every frame and flip it horizontally. It looks done. It is not.
A flipped frame mirrors everything. The search icon points the wrong way, clock hands run backwards, the logo reads in reverse. And mirroring moves things; it does not re-space them.
The fix is a mental one. Stop thinking "align left, align right". Think "align start, align end".
In LTR, start is left. In RTL, start is right. Design with start and end, and the layout follows the reading direction on its own. I bring this to developers early, so the code uses margin-inline-start instead of margin-left from day one.
A page in pure Arabic is fine. Real content is mixed: an English place name inside an Arabic sentence, a price, a URL, a "Book now" button next to Arabic copy. Two directions on one line is called bidirectional text, and it breaks in odd ways. So the spec gets hard rules:
I do not read Arabic, so I cannot see half the problems. A layout can look right to me and still read wrong. A native reader checks every round before anything goes to the client.
AI can draft the lists and the test strings. It cannot vouch for the grammar, and it will not be in the meeting explaining the design. I will.
Email me, or follow on LinkedIn where new notes land first. No newsletter, no pop-up, promise.