<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fahhim Blog - Arabic AI Prompt Engineering</title>
    <link>https://fahhim.moteklab.com/blog</link>
    <description>Structured prompt engineering frameworks for Arabic &amp; English AI communication. COSTAR, ICDF, MICRO, RCR-EOC and more.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 07 Nov 2026 01:29:42 GMT</lastBuildDate>
    <atom:link href="https://fahhim.moteklab.com/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Egyptian Arabic Prompt Engineering: A Complete Guide</title>
      <link>https://fahhim.moteklab.com/blog/egyptian-arabic-prompt-engineering</link>
      <guid isPermaLink="true">https://fahhim.moteklab.com/blog/egyptian-arabic-prompt-engineering</guid>
      <description>Master the nuances of Egyptian dialect in AI prompts. Learn how to craft prompts that produce authentic, culturally-aware responses.</description>
      <pubDate>Sat, 07 Nov 2026 01:29:42 GMT</pubDate>
      <author>Motaz Hefny &lt;motaz@fahhim.moteklab.com&gt;</author>
      <category>machinelearning</category>
      <category>ai</category>
      <category>egyptian-arabic</category>
    </item>
    <item>
      <title>Why Arabic breaks most prompt templates — here is the structure that survives</title>
      <link>https://fahhim.moteklab.com/blog/costar-framework-guide</link>
      <guid isPermaLink="true">https://fahhim.moteklab.com/blog/costar-framework-guide</guid>
      <description>Most English prompt engineering frameworks assume Roman-alphabet semantics. When you apply them to Arabic text—especially Egyptian dialect—you get structural collapse: pronoun ambiguity, gender agreement failures, and missing context markers.</description>
      <pubDate>Fri, 06 Nov 2026 23:56:40 GMT</pubDate>
      <author>Motaz Hefny &lt;motaz@fahhim.moteklab.com&gt;</author>
      <category>ai</category>
      <category>prompt-engineering</category>
      <category>arabic</category>
    </item>
  </channel>
</rss>