<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Snapflow Blog</title>
    <link>https://www.snapflow.design/en/blog.html</link>
    <description>A design system is not documentation. It is infrastructure that runs. We write about how to build one that way: tokens, tools and the path from Figma to production code.</description>
    <language>en</language>
    <lastBuildDate>Wed, 21 Oct 2026 12:00:00 GMT</lastBuildDate>
    <atom:link href="https://www.snapflow.design/en/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>What is an agentic design system</title>
      <link>https://www.snapflow.design/en/blog/agentic-design-system.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/agentic-design-system.html</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>An agentic design system is one your AI agent can read and use: tokens, components and rules that generate consistent screens and code instead of guessing them. What it is and how to adopt it.</description>
      <category>Agentic</category>
    </item>
    <item>
      <title>What is Snapflow</title>
      <link>https://www.snapflow.design/en/blog/snapflow.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/snapflow.html</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>An agentic design system already built, with your brand in seven steps, in React, Vue 3 and Angular, used by your agent via MCP. What it delivers and costs.</description>
      <category>Agentic</category>
    </item>
    <item>
      <title>Figma to code: why the code never matches the design</title>
      <link>https://www.snapflow.design/en/blog/figma-to-code.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/figma-to-code.html</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>What figma to code is, why plugins and AI generate code that does not match the design, and how to avoid it when Figma and the code share the same components.</description>
      <category>Figma to code</category>
    </item>
    <item>
      <title>Figma to code tools compared: Anima, Locofy, Builder.io and Dev Mode</title>
      <link>https://www.snapflow.design/en/blog/figma-to-code-tools-compared.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/figma-to-code-tools-compared.html</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>An honest comparison of Anima, Locofy, Builder.io and Figma Dev Mode: where each one wins, what none does, and the axis that decides: pixels or components.</description>
      <category>Figma to code</category>
    </item>
    <item>
      <title>Design Tokens: What They Are, the Standard, and How They Reach Code</title>
      <link>https://www.snapflow.design/en/blog/design-tokens.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/design-tokens.html</guid>
      <pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
      <description>Design tokens explained: what they are, the three tiers, naming by intent, the new W3C standard, and the pipeline that turns a token file into production code.</description>
      <category>Foundations</category>
    </item>
    <item>
      <title>How we compile a design system to 3 frameworks</title>
      <link>https://www.snapflow.design/en/blog/blog-4-frameworks.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/blog-4-frameworks.html</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>The same component, in React, Vue 3 and Angular. These are not three libraries maintained by hand: it is one definition and three outputs.</description>
      <category>Agentic</category>
    </item>
    <item>
      <title>How to Build a Design System: Complete Guide for Design Teams</title>
      <link>https://www.snapflow.design/en/blog/how-to-build-a-design-system.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/how-to-build-a-design-system.html</guid>
      <pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
      <description>A practical guide to building design systems that actually scale, from token architecture to governance. Learn the infrastructure-first approach used by enterprise teams.</description>
      <category>Foundations</category>
    </item>
    <item>
      <title>zeroheight Alternative: Documentation vs. Design System Infrastructure</title>
      <link>https://www.snapflow.design/en/blog/zeroheight-alternative.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/zeroheight-alternative.html</guid>
      <pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
      <description>Looking for a zeroheight alternative? The real documentation options, and when the gap is not docs at all but infrastructure that generates your code.</description>
      <category>Tools</category>
    </item>
    <item>
      <title>Supernova vs zeroheight: Which Design System Platform (2026)</title>
      <link>https://www.snapflow.design/en/blog/supernova-vs-zeroheight.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/supernova-vs-zeroheight.html</guid>
      <pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
      <description>Supernova vs zeroheight, compared honestly: documentation, token automation, setup, and code. What each wins, and the job neither is built to do.</description>
      <category>Tools</category>
    </item>
    <item>
      <title>Design System Tools: What Each One Does and What&apos;s Missing</title>
      <link>https://www.snapflow.design/en/blog/design-system-tools.html</link>
      <guid isPermaLink="true">https://www.snapflow.design/en/blog/design-system-tools.html</guid>
      <pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
      <description>Design system tools each manage one slice; infrastructure owns the result. The categories, where they break, and how to choose for enterprise teams.</description>
      <category>Tools</category>
    </item>
  </channel>
</rss>
