Voice

Read when: you write any text in his name, in English or Arabic: a page, a caption, a post, a bio. Owns: the voice, the rules for English and Arabic, the words to avoid, the bios, and the honesty rules.

His readers include CEOs, CTOs, engineers and recruiters; write so all of them follow. Name, title and handle are in ../SKILL.md. Checked 2026-11-03 against the site's brand page.

TL;DR

• Plain words over jargon. Show the work before the title. Warm, never loud.
• Short sentences, one idea per paragraph, first person for his own work.
• No marketing words and no claim that can't be traced to code, history or a measurement.
• English: British spelling in new text, sentence case for headings and buttons.
• Arabic: simple Modern Standard Arabic, technical names in Latin letters, Latin digits.

Rules for both languages

• Short sentences. One idea per paragraph.
• First person for his own work ("I designed and built..."). "The team" for shared work.
• If a sentence still works without the adjective, drop the adjective.
• Headings say plainly what the section is ("The import engine", not "One engine to rule them all").
• Technical depth (how it is built, step by step) belongs in articles, not on cards or summaries.

English

• British spelling in new text: colour, behaviour, organisation, authorise. Don't churn existing pages to change it.
• Sentence case for headings, buttons and running text ("senior software engineer").
• Meta lines use a middle dot with spaces: Article · Laravel, JUL 2023 · laravel/framework #46405.
• Words to avoid: cutting-edge, seamless, robust, blazing, revolutionary, world-class, leverage, empower, unlock, game-changing, next-level, supercharge.
• Filler to avoid: "In today's fast-paced world", "It's worth noting", "Let's dive in", groups of three added for rhythm, a closing line that repeats the post.

Arabic

Register: simple Modern Standard Arabic (فصحى بسيطة), not classical and not dialect. The everyday word over the literary one, one fixed term per concept.

• His name, handle and domain stay in Latin letters. Ask him before using an Arabic spelling of the name.
• Technical names stay in Latin letters (Laravel, API, Nuxt).
• Numbers in Latin digits: 30 يوماً، 6 ساعات.
• First person for his own work: «صممتُ وبنيتُ ...». Shared work: «الفريق».
• Words to avoid: ثوري، لا مثيل له، الأفضل على الإطلاق، سلس تماماً، قوي جداً، نقلة نوعية، متكامل وشامل.
• The tone, by example:
  • «أنشئ الفاتورة وأرسلها إلى العميل في خطوة واحدة. تبقى نسخة منها في حسابك.»
  • Not: «منصة ثورية متكاملة تمنحك تجربة سلسة لا مثيل لها في إدارة فواتيرك.»

Bios

Bios are in the third person; posts and his own pages use the first person.

Short bio (about 40 words):

Haytham A. Salama is a senior software engineer who builds SaaS, logistics and fintech platforms. He contributes to Nuxt UI, writes about shipping software, and works every day alongside AI coding agents.

Long bio (about 80 words):

Haytham A. Salama is a senior software engineer who has been shipping software since 2016. He designs systems around the domain, builds the APIs, integrations and security they run on, and leads small teams that take them to production. Before code, he repaired electronics and worked as a designer and video editor, which still shapes how his software feels. He has contributed to Laravel, Nuxt and Nuxt UI, and works every day alongside AI coding agents.

Honesty

• Every claim can be traced to code, git history or a measurement. If it can't, ask him; don't invent it.
• Say exactly what he did: "I designed and built X", "I built the foundation of X; the team grew it".
• No unmeasured outcomes ("3× faster" only when it was measured).
• Nothing internal to an employer or a client: no secrets, internal numbers, screenshots or code.

Before publishing

• [ ] Read it aloud. Anything that sounds like an advert gets rewritten.
• [ ] Every claim can be traced to code, history or a measurement.
• [ ] Name, title and handle are spelled as in ../SKILL.md.
• [ ] Arabic text is simple فصحى, with Latin digits.