<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ahmed Amr | Writing</title>
    <link>https://www.ahmedamr.com/writing</link>
    <description>Design that moves the business. Code that ships it. Product, interaction and UI design across fintech, Web3, food delivery and internal operations tools.</description>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://www.ahmedamr.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A design system is a set of decisions, and the code is where they live</title>
      <link>https://www.ahmedamr.com/writing/why-design-system-in-code</link>
      <guid isPermaLink="true">https://www.ahmedamr.com/writing/why-design-system-in-code</guid>
      <description>Why products drift apart without a design system, why a mockup leaves most of a button undecided, and what a designer gains by knowing where each decision lives in code. The first part of a series.</description>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Decide the switches first, and the folders follow</title>
      <link>https://www.ahmedamr.com/writing/design-system-repository-setup</link>
      <guid isPermaLink="true">https://www.ahmedamr.com/writing/design-system-repository-setup</guid>
      <description>Before the first token, decide which switches the product needs, brand, light or dark, language, and let them shape the folders. Then the scaffold, GitHub, a check on every pull request and the first rules for the agent, one prompt at a time.</description>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>