<?xml version="1.0" encoding="UTF-8"?>
<urlset
  xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
  xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
  xmlns:xhtml="http://www.w3.org/1999/xhtml"
>
  <url>
    <loc>https://atomize.tools/</loc>
    <lastmod>2026-05-06</lastmod>
    <priority>1.0</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/"/>
  </url>
  <url>
    <loc>https://atomize.tools/es/</loc>
    <lastmod>2026-05-06</lastmod>
    <priority>1.0</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/"/>
  </url>
  <url>
    <loc>https://atomize.tools/blog/</loc>
    <lastmod>2026-06-05</lastmod>
    <priority>0.9</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/"/>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/</loc>
    <lastmod>2026-06-05</lastmod>
    <priority>0.9</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/"/>
  </url>
  <url>
    <loc>https://atomize.tools/author/vitalina-makus/</loc>
    <lastmod>2026-05-06</lastmod>
    <priority>0.75</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/author/vitalina-makus/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/author/vitalina-makus/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/author/vitalina-makus/"/>
  </url>
  <url>
    <loc>https://atomize.tools/es/author/vitalina-makus/</loc>
    <lastmod>2026-05-06</lastmod>
    <priority>0.75</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/author/vitalina-makus/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/author/vitalina-makus/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/author/vitalina-makus/"/>
  </url>
  <url>
    <loc>https://atomize.tools/about/</loc>
    <lastmod>2026-05-28</lastmod>
    <priority>0.7</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/about/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/about/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/about/"/>
  </url>
  <url>
    <loc>https://atomize.tools/es/about/</loc>
    <lastmod>2026-05-28</lastmod>
    <priority>0.7</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/about/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/about/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/about/"/>
  </url>
  <url>
    <loc>https://atomize.tools/faq/</loc>
    <lastmod>2026-05-28</lastmod>
    <priority>0.7</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/faq/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/faq/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/faq/"/>
  </url>
  <url>
    <loc>https://atomize.tools/es/faq/</loc>
    <lastmod>2026-05-28</lastmod>
    <priority>0.7</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/faq/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/faq/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/faq/"/>
  </url>
  <url>
    <loc>https://atomize.tools/privacy/</loc>
    <lastmod>2026-05-06</lastmod>
    <priority>0.6</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/privacy/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/privacy/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/privacy/"/>
  </url>
  <url>
    <loc>https://atomize.tools/es/privacy/</loc>
    <lastmod>2026-05-06</lastmod>
    <priority>0.6</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/privacy/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/privacy/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/privacy/"/>
  </url>
  <url>
    <loc>https://atomize.tools/blog/learn/</loc>
    <lastmod>2026-06-01</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/learn/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/learn/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/learn/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Learn-Why-design-systems-in-Figma.webp</image:loc>
      <image:title>learn</image:title>
      <image:caption>learn</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/learn/</loc>
    <lastmod>2026-06-01</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/learn/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/learn/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/learn/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Learn-Why-design-systems-in-Figma-es.webp</image:loc>
      <image:title>learn</image:title>
      <image:caption>learn</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/build/</loc>
    <lastmod>2026-06-01</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/build/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/build/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/build/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Build-Structure-tokens-Variables.webp</image:loc>
      <image:title>build</image:title>
      <image:caption>build</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/build/</loc>
    <lastmod>2026-06-01</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/build/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/build/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/build/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Build-Structure-tokens-Variables-es.webp</image:loc>
      <image:title>build</image:title>
      <image:caption>build</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/audit/</loc>
    <lastmod>2026-05-30</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/audit/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/audit/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/audit/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Audit-Coverage-drift-accessibility.webp</image:loc>
      <image:title>audit</image:title>
      <image:caption>audit</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/audit/</loc>
    <lastmod>2026-05-30</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/audit/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/audit/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/audit/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Audit-Coverage-drift-accessibility-es.webp</image:loc>
      <image:title>audit</image:title>
      <image:caption>audit</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/ship/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/ship/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/ship/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/ship/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Ship-Design-to-code-parity.webp</image:loc>
      <image:title>ship</image:title>
      <image:caption>ship</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/ship/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/ship/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/ship/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/ship/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Ship-Design-to-code-parity-es.webp</image:loc>
      <image:title>ship</image:title>
      <image:caption>ship</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/edge/</loc>
    <lastmod>2026-06-05</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/edge/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/edge/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/edge/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Edge-AI-MCP-tools.webp</image:loc>
      <image:title>edge</image:title>
      <image:caption>edge</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/edge/</loc>
    <lastmod>2026-06-05</lastmod>
    <priority>0.85</priority>
    <changefreq>weekly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/edge/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/edge/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/edge/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Edge-AI-MCP-tools-es.webp</image:loc>
      <image:title>edge</image:title>
      <image:caption>edge</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/ai-skills-for-designers/</loc>
    <lastmod>2026-06-05</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/ai-skills-for-designers/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/ai-skills-for-designers/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/ai-skills-for-designers/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/AI-Skills-for-Designers-Claude-Code-Cursor-Tokens.webp</image:loc>
      <image:title>Claude Skills vs Cursor Rules | AI Workflows for Designers</image:title>
      <image:caption>What broke when we added Claude skills without tokens: PR case study, AGENTS.md, Cursor rules, and a workflow checklist.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/ai-skills-for-designers/</loc>
    <lastmod>2026-06-05</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/ai-skills-for-designers/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/ai-skills-for-designers/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/ai-skills-for-designers/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/AI-Skills-for-Designers-Claude-Code-Cursor-Tokens-es.webp</image:loc>
      <image:title>Claude Skills vs Cursor Rules | Workflows de IA para Diseñadores</image:title>
      <image:caption>Qué falló al añadir Claude skills sin tokens: caso PR, AGENTS.md, reglas de Cursor y checklist de workflow.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-design-tokens-vibe-coding/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-tokens-vibe-coding/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-tokens-vibe-coding/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-tokens-vibe-coding/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-design-tokens-vibe-coding.webp</image:loc>
      <image:title>Design System AI Workflows | AI Code Generation &amp; Figma Tokens</image:title>
      <image:caption>AI coding assistants ignore Figma tokens without repo context. DTCG, Style Dictionary, AGENTS.md for design system AI workflows.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-design-tokens-vibe-coding/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-tokens-vibe-coding/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-tokens-vibe-coding/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-tokens-vibe-coding/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/figma-design-tokens-vibe-coding-es.webp</image:loc>
      <image:title>Flujos de IA del Sistema de Diseño | Generación de Código IA y Tokens Figma</image:title>
      <image:caption>Los asistentes IA ignoran design tokens de Figma sin contexto en el repo. DTCG, Style Dictionary y AGENTS.md para flujos de IA del sistema de diseño.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/design-system-maturity/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/design-system-maturity/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/design-system-maturity/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/design-system-maturity/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Design-System-Maturity-5-Levels-Explained.webp</image:loc>
      <image:title>Design System Maturity Levels: A Practical Guide</image:title>
      <image:caption>Five design system maturity levels from UI kit to public platform. Scorecard, examples, and how to measure where your team sits today.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/ds-maturity-levels.webp</image:loc>
      <image:title>Design system maturity model showing 5 levels: UI Kit, Design Library, Design System (highlighted), Scaled System, and Public System with key capabilities at each stage</image:title>
      <image:caption>Level 3 is the key transition - where design tokens connect to code and the system gains a dedicated owner.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/design-system-maturity/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/design-system-maturity/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/design-system-maturity/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/design-system-maturity/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Design-System-Maturity-5-Levels-Explained-es.webp</image:loc>
      <image:title>Niveles de Madurez del Sistema de Diseño: Guía Práctica</image:title>
      <image:caption>Cinco niveles de madurez del sistema de diseño, desde kit UI hasta plataforma pública. Scorecard, ejemplos y cómo medir dónde está tu equipo.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/ds-maturity-levels.webp</image:loc>
      <image:title>Modelo de madurez del sistema de diseño que muestra 5 niveles: Kit de UI, Biblioteca de Diseño, Sistema de Diseño (resaltado), Sistema Escalado y Sistema Público con capacidades clave en cada etapa</image:title>
      <image:caption>El Nivel 3 es la transición clave - donde los tokens de diseño se conectan al código y el sistema obtiene un propietario dedicado.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/claude-design/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/claude-design/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/claude-design/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/claude-design/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Claude-Design-What-It-Is-and-How-It-Works.webp</image:loc>
      <image:title>Claude Design Explained: Features, Design Systems, Handoff</image:title>
      <image:caption>Claude Design launched April 2026. Learn what it extracts from design systems, how Claude Code handoff works, and where Figma still wins.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/claude-design/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/claude-design/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/claude-design/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/claude-design/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Claude-Design-What-It-Is-and-How-It-Works-es.webp</image:loc>
      <image:title>Claude Design Explicado: Funciones, Sistemas de Diseño, Entrega</image:title>
      <image:caption>Claude Design (2026): qué extrae de tu sistema de diseño, handoff con Claude Code y por qué Figma sigue siendo la fuente de verdad.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/design-system/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/design-system/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/design-system/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/design-system/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/What-Is-a-Design-System.webp</image:loc>
      <image:title>What Is a Design System? Definition, Layers &amp; Failure Modes</image:title>
      <image:caption>A design system is tokens, components, patterns, and docs that keep UI consistent at scale. Learn what it includes, how it fails, and when to build one.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/ds-four-layers.webp</image:loc>
      <image:title>The four layers of a design system: Design Tokens at the foundation, then Component Library, Patterns, and Documentation at the top</image:title>
      <image:caption>The four layers of a design system - each layer depends on the one below it.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/ds-token-architecture.webp</image:loc>
      <image:title>Design token architecture diagram showing primitive tokens aliasing to semantic tokens, which resolve to different values in Light and Dark modes</image:title>
      <image:caption>Primitive tokens hold raw values; semantic tokens alias primitives and resolve differently per mode. Components bind to semantic tokens - never to primitives directly.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/design-system/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/design-system/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/design-system/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/design-system/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/What-Is-a-Design-System-es.webp</image:loc>
      <image:title>¿Qué Es un Sistema de Diseño? Definición, Capas y Modos de Fallo</image:title>
      <image:caption>Qué es un sistema de diseño: tokens, componentes y documentación para UI coherente. Cuándo construirlo en Figma y guías en español.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/ds-four-layers.webp</image:loc>
      <image:title>Las cuatro capas de un sistema de diseño: Design Tokens en la base, luego Biblioteca de Componentes, Patrones y Documentación arriba</image:title>
      <image:caption>Las cuatro capas de un sistema de diseño - cada capa depende de la inferior.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/ds-token-architecture.webp</image:loc>
      <image:title>Diagrama de arquitectura de tokens mostrando primitivos que aliasan a semánticos con valores distintos en modos Claro y Oscuro</image:title>
      <image:caption>Los primitivos guardan valores en bruto; los semánticos aliasan primitivos y resuelven distinto por modo. Los componentes usan solo semánticos.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-mcp/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-mcp/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-mcp/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-mcp/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Figma-MCP-Dev-Mode-Server-Guide-for-Designers.webp</image:loc>
      <image:title>Figma MCP - Dev Mode Server Guide for Designers by Atomize</image:title>
      <image:caption>Figma MCP is the Dev Mode server that lets AI tools like Claude and Cursor read your file as structured tokens and layout - not screenshots.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-mcp-architecture.webp</image:loc>
      <image:title>Diagram of the Figma MCP architecture - four cards left to right showing Figma File with Variables and components, Dev Mode MCP local server exposing structured JSON, AI Client like Claude or Cursor reading the file directly, and Production Code output as tokenized React, CSS, or Tailwind</image:title>
      <image:caption>Figma MCP turns the design-to-code handoff into a live channel. The Dev Mode server reads the selection, ships structured context to the AI client, and the model writes code that uses your real token names.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-mcp/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-mcp/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-mcp/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-mcp/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Figma-MCP-Dev-Mode-Server-Guide-for-Designers-es.webp</image:loc>
      <image:title>Figma MCP - Guía del Servidor Dev Mode para Diseñadores por Atomize</image:title>
      <image:caption>Figma MCP es el servidor Dev Mode que permite a Claude y Cursor leer tu archivo como tokens estructurados y layout, no capturas de pantalla.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-mcp-architecture.webp</image:loc>
      <image:title>Diagrama de la arquitectura Figma MCP - cuatro tarjetas de izquierda a derecha mostrando Archivo de Figma con Variables y componentes, servidor local MCP Dev Mode que expone JSON estructurado, Cliente de IA como Claude o Cursor leyendo el archivo directamente, y salida de Código de Producción como React, CSS o Tailwind tokenizado</image:title>
      <image:caption>Figma MCP convierte la entrega de diseño a código en un canal en vivo. El servidor Dev Mode lee la selección, envía contexto estructurado al cliente de IA, y el modelo escribe código que usa tus nombres de tokens reales.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-contrast-audit/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-contrast-audit/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-contrast-audit/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-contrast-audit/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Figma-Contrast-Audit-Find-WCAG-Failures-at-Scale.webp</image:loc>
      <image:title>Figma Library &amp; Contrast Audit: Bulk WCAG Check (Atomize)</image:title>
      <image:caption>Bulk WCAG contrast audit for Figma - scans your library for AA failures, grouped by design token so one fix resolves every affected component.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/contrast-audit.webp</image:loc>
      <image:title>Atomize Contrast Audit results panel showing WCAG findings grouped by Text, Background, Shape, and Border with contrast ratios, A and AA pass/fail badges, foreground and background swatches per row, Skip and Skip-all controls, and an Export Issues Report button at the bottom</image:title>
      <image:caption>Contrast Audit groups failing layers by element type. Each row shows the ratio, the foreground and background colors, A and AA pass/fail badges, and a Skip control for intentional cases like decorative gradients.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-contrast-audit/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-contrast-audit/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-contrast-audit/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-contrast-audit/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Figma-Contrast-Audit-Find-WCAG-Failures-at-Scale-es.webp</image:loc>
      <image:title>Auditoría de Contraste en Figma - Verificación WCAG Masiva por Atomize</image:title>
      <image:caption>Atomize escanea Figma en busca de fallos WCAG AA en texto, rellenos y trazos, y agrupa los resultados por token, no por capa.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/contrast-audit.webp</image:loc>
      <image:title>Panel de resultados de Atomize Contrast Audit mostrando hallazgos WCAG agrupados por Texto, Fondo, Forma y Borde con relaciones de contraste, insignias de aprobado/reprobado A y AA, muestras de color de primer plano y fondo por fila, controles Skip y Skip-all, y botón Export Issues Report en la parte inferior</image:title>
      <image:caption>Contrast Audit agrupa las capas que fallan por tipo de elemento. Cada fila muestra la relación, los colores de primer plano y fondo, insignias de aprobado/reprobado A y AA, y un control Skip para casos intencionales como degradados decorativos.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/find-untokenized-values-figma/</loc>
    <lastmod>2026-05-28</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/find-untokenized-values-figma/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/find-untokenized-values-figma/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/find-untokenized-values-figma/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Find-Untokenized-Values-in-Figma-Token-Coverage-Audit.webp</image:loc>
      <image:title>Find Untokenized Values in Figma - Atomize Token Audit</image:title>
      <image:caption>Find untokenized values in Figma: token vs literal without Variables. Atomize audits fills, padding, radius, and typography.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/find-untokenized-values.webp</image:loc>
      <image:title>Atomize Find Untokenized Values results panel showing groups for Fill, Opacity, Border-radius, Margin, Gap, Padding, Stroke weight, Effects, and Font-family with per-group counts, an expanded Ellipse fill of #505A73, an expanded Frame opacity of 40%, Skip controls, and an Export Report button</image:title>
      <image:caption>The results panel groups findings by property category. Each row shows the node, its layer path, the page, and the raw value - with Skip per item, Skip all per group, and Export Report at the bottom.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/find-untokenized-values-figma/</loc>
    <lastmod>2026-05-28</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/find-untokenized-values-figma/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/find-untokenized-values-figma/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/find-untokenized-values-figma/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Find-Untokenized-Values-in-Figma-Token-Coverage-Audit-es.webp</image:loc>
      <image:title>Encontrar Valores No Tokenizados en Figma - Auditoría de Tokens de Atomize</image:title>
      <image:caption>Encuentra valores no tokenizados en Figma: token vinculado vs literal sin Variable. Atomize audita rellenos, espaciado, radio y tipografía.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/find-untokenized-values.webp</image:loc>
      <image:title>Panel de resultados de Atomize Find Untokenized Values mostrando grupos para Relleno, Opacidad, Radio de borde, Margen, Espacio, Relleno, Grosor de trazo, Efectos y Familia tipográfica con conteos por grupo, un relleno de Elipse expandido de #505A73, una opacidad de Frame expandida del 40%, controles Skip y botón Export Report</image:title>
      <image:caption>El panel de resultados agrupa los hallazgos por categoría de propiedad. Cada fila muestra el nodo, su ruta de capa, la página y el valor bruto - con Skip por elemento, Skip all por grupo y Export Report en la parte inferior.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-vs-pencil-design-system/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-vs-pencil-design-system/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-vs-pencil-design-system/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-vs-pencil-design-system/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Figma-vs-Pencil-Which-Tool-Is-Better-for-Design-Systems.webp</image:loc>
      <image:title>Pencil vs Figma (2026): Design System Tools Compared</image:title>
      <image:caption>Pencil vs Figma for design systems in 2026: IDE-native .pen files vs collaborative Variables, MCP, tokens, and which tool fits your team.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-vs-pencil-comparison.webp</image:loc>
      <image:title>Figma vs Pencil: Figma is a browser-based collaborative design tool, Pencil is an IDE extension with AI-driven design canvas</image:title>
      <image:caption>Different tools for different teams - Figma for designer-led workflows, Pencil for developer-led design inside the IDE.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-vs-pencil-design-system/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-vs-pencil-design-system/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-vs-pencil-design-system/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-vs-pencil-design-system/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Figma-vs-Pencil-Which-Tool-Is-Better-for-Design-Systems-es.webp</image:loc>
      <image:title>Pencil vs Figma (2026): Herramientas para Sistemas de Diseño</image:title>
      <image:caption>Pencil vs Figma para design systems en 2026: archivos .pen en el IDE vs Variables colaborativas, MCP, tokens y qué herramienta encaja en tu equipo.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-vs-pencil-comparison.webp</image:loc>
      <image:title>Figma vs Pencil: Figma es una herramienta de diseño colaborativa basada en navegador, Pencil es una extensión de IDE con lienzo de diseño impulsado por IA</image:title>
      <image:caption>Herramientas diferentes para equipos diferentes - Figma para flujos con diseñadores, Pencil para diseño liderado por desarrollo en el IDE.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-variables-dark-mode/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-variables-dark-mode/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-variables-dark-mode/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-variables-dark-mode/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/How-to-Create-Dark-Mode-in-Figma-with-Variables.webp</image:loc>
      <image:title>Figma Dark Mode with Variables: Step-by-Step Guide (2026)</image:title>
      <image:caption>Add dark and light mode in Figma with Variables - semantic aliases, two-collection setup, and theme switching without touching a single component.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-dark-mode-variables-comparison.webp</image:loc>
      <image:title>Light Mode vs Dark Mode comparison showing how the same semantic tokens resolve to different color values in each mode</image:title>
      <image:caption>Same semantic token names, different values per mode. Switch mode in Figma and all components update automatically.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-variables-dark-mode/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-variables-dark-mode/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-variables-dark-mode/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-variables-dark-mode/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/How-to-Create-Dark-Mode-in-Figma-with-Variables-es.webp</image:loc>
      <image:title>Modo Oscuro en Figma con Variables: Guía Paso a Paso (2026)</image:title>
      <image:caption>Modo oscuro en Figma con Variables: dos colecciones, alias semánticos, export CSS y cambio de tema sin repintar componentes.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-dark-mode-variables-comparison.webp</image:loc>
      <image:title>Comparación entre Modo Claro y Modo Oscuro mostrando cómo los mismos tokens semánticos se resuelven en diferentes valores de color en cada modo</image:title>
      <image:caption>Los mismos nombres de tokens semánticos, diferentes valores por modo. Cambia el modo en Figma y todos los componentes se actualizan automáticamente.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-design-system-parity-code-sync/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-system-parity-code-sync/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-system-parity-code-sync/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-system-parity-code-sync/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Design-System-Parity-Figma-&amp;-Code-What-Actually-Works.webp</image:loc>
      <image:title>Design System Parity: Figma vs Code Sync in 2026</image:title>
      <image:caption>Why Figma-to-code parity keeps breaking - token sync works, component-level automation doesn't, and MCP workflows fill the gap in 2026.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-ds-token-sync-pipeline.webp</image:loc>
      <image:title>Design-to-code token sync pipeline: Figma Variables exported via Atomize to JSON/CSS/TypeScript, reviewed in a PR, and shipped to production</image:title>
      <image:caption>The token sync pipeline - changes in Figma Variables flow through an export step, a code review, and land in production with zero manual copy-paste.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-design-system-parity-code-sync/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-system-parity-code-sync/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-system-parity-code-sync/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-system-parity-code-sync/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Design-System-Parity-Figma-&amp;-Code-What-Actually-Works-es.webp</image:loc>
      <image:title>Paridad del Sistema de Diseño: Sincronización Figma vs Código en 2026</image:title>
      <image:caption>Por qué la paridad Figma-código sigue rompiéndose - y qué funciona: sincronización de tokens, flujos MCP, límites de componentes y gobernanza.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-ds-token-sync-pipeline.webp</image:loc>
      <image:title>Canalización de sincronización de tokens de diseño a código: Variables de Figma exportadas via Atomize a JSON/CSS/TypeScript, revisadas en un PR y lanzadas a producción</image:title>
      <image:caption>La canalización de sincronización de tokens - los cambios en las Variables de Figma fluyen a través de un paso de exportación, una revisión de código y aterrizan en producción sin copiar y pegar manualmente.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-plugins-design-system-token-workflows/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-plugins-design-system-token-workflows/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-plugins-design-system-token-workflows/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-plugins-design-system-token-workflows/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Figma-Plugins-for-Tokens-Git-Sync-Design-Workflows.webp</image:loc>
      <image:title>Best Figma Plugins for Design Tokens (2026): Export &amp; Git</image:title>
      <image:caption>Best Figma plugins for design token export, Git sync, and DTCG in 2026. Compare Tokens Studio, Atomize, and Variables Sync for your stack.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-plugins-categories.webp</image:loc>
      <image:title>Six categories of Figma plugins for design system workflows: Token Export, Design QA, Code Sync, Documentation, Utilities, and AI &amp; MCP</image:title>
      <image:caption>Design system plugin work splits into six distinct categories - each solves a different part of the token and component pipeline.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-plugins-design-system-token-workflows/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-plugins-design-system-token-workflows/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-plugins-design-system-token-workflows/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-plugins-design-system-token-workflows/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Figma-Plugins-for-Tokens-Git-Sync-Design-Workflows-es.webp</image:loc>
      <image:title>Los Mejores Plugins de Figma para Design Tokens 2026: Exportación, Sync y Git</image:title>
      <image:caption>Mejores plugins de Figma para exportar tokens, sync con Git y DTCG en 2026. Compara Tokens Studio, Atomize y Variables Sync para tu stack.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-plugins-categories.webp</image:loc>
      <image:title>Seis categorías de plugins de Figma para flujos de trabajo de sistemas de diseño: Exportación de Tokens, QA de Diseño, Sincronización de Código, Documentación, Utilidades e IA y MCP</image:title>
      <image:caption>El trabajo de plugins de sistemas de diseño se divide en seis categorías distintas - cada una resuelve una parte diferente de la canalización de tokens y componentes.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/what-is-design-system-figma/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/what-is-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/what-is-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/what-is-design-system-figma/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/What-Is-a-Design-System-in-Figma-A-Practical-Guide.webp</image:loc>
      <image:title>What Is a Design System in Figma? Complete Guide</image:title>
      <image:caption>What a Figma design system is: Variables, components, governance, and when Figma is the right home - plus when it is not enough.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/what-is-ds-four-components.webp</image:loc>
      <image:title>The four layers of a Figma design system: Design Tokens, Component Library, Patterns, and Documentation</image:title>
      <image:caption>Every mature design system has four layers - each adds more value and more maintenance responsibility.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/what-is-design-system-figma/</loc>
    <lastmod>2026-05-31</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/what-is-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/what-is-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/what-is-design-system-figma/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/What-Is-a-Design-System-in-Figma-A-Practical-Guide-es.webp</image:loc>
      <image:title>¿Qué Es un Sistema de Diseño en Figma? Guía Completa</image:title>
      <image:caption>Qué es un sistema de diseño en Figma: Variables, componentes, gobernanza y cuándo Figma basta - y cuándo no.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/what-is-ds-four-components.webp</image:loc>
      <image:title>Las cuatro capas de un sistema de diseño de Figma: tokens, biblioteca, patrones y documentación</image:title>
      <image:caption>Cada sistema maduro tiene cuatro capas - cada una añade valor y responsabilidad de mantenimiento.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/how-to-build-design-system-figma/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/how-to-build-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/how-to-build-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/how-to-build-design-system-figma/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/How-to-Build-a-Design-System-in-Figma-Step-by-Step.webp</image:loc>
      <image:title>How to Build a Figma Design System: Step-by-Step</image:title>
      <image:caption>Step-by-step Figma design system: audit, Variables &amp; token layers, core components, docs, team publish, governance, and code sync.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-ds-build-process-phases.webp</image:loc>
      <image:title>Three-phase design system build process: Foundation (tokens and Variables), Components (auto-layout, variants, library), and Govern (owner, code sync, docs)</image:title>
      <image:caption>Three phases to a production design system - Foundation first, then Components, then Governance. Each phase builds on the last.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/how-to-build-design-system-figma/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/how-to-build-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/how-to-build-design-system-figma/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/how-to-build-design-system-figma/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/How-to-Build-a-Design-System-in-Figma-Step-by-Step-es.webp</image:loc>
      <image:title>Cómo Construir un Sistema de Diseño en Figma: Paso a Paso</image:title>
      <image:caption>Cómo construir un sistema de diseño en Figma: auditoría, Variables, tokens, componentes, documentación, gobernanza y sincronización de código.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-ds-build-process-phases.webp</image:loc>
      <image:title>Proceso de construcción de sistema de diseño en tres fases: Fundamento (tokens y Variables), Componentes (auto-layout, variantes, biblioteca) y Gobernanza (propietario, sincronización de código, documentación)</image:title>
      <image:caption>Tres fases para un sistema de diseño de producción - Fundamento primero, luego Componentes, luego Gobernanza. Cada fase se construye sobre la anterior.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-coverage-audit-vs-untokenized-values/</loc>
    <lastmod>2026-05-30</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-coverage-audit-vs-untokenized-values/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-coverage-audit-vs-untokenized-values/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-coverage-audit-vs-untokenized-values/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Coverage-Audit-vs-Untokenized-in-Figma.webp</image:loc>
      <image:title>Figma Token Coverage vs Untokenized Values</image:title>
      <image:caption>Compare Figma Coverage Audit vs Find Untokenized Values: binding rate, hardcoded literals, token adoption, and run order before contrast.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-coverage-audit-vs-untokenized-values/</loc>
    <lastmod>2026-05-30</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-coverage-audit-vs-untokenized-values/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-coverage-audit-vs-untokenized-values/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-coverage-audit-vs-untokenized-values/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Coverage-Audit-vs-Untokenized-in-Figma-es.webp</image:loc>
      <image:title>Cobertura de Tokens vs Valores No Tokenizados</image:title>
      <image:caption>Compara Coverage Audit vs Find Untokenized Values en Figma: vinculación, literales codificados, adopción de tokens y orden antes del contraste.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-design-tokens-guide/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-tokens-guide/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-tokens-guide/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-tokens-guide/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Figma-Design-Tokens-The-Complete-Guide-for-UI-UX-Designers.webp</image:loc>
      <image:title>Figma Design Tokens Guide (2026): Variables to Code</image:title>
      <image:caption>Complete 2026 guide to Figma design tokens: Variables, primitives, semantic aliases, dark mode, DTCG export, and CSS/TypeScript handoff for UI teams.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-tokens-two-layer-architecture.webp</image:loc>
      <image:title>Two-layer token architecture: Primitive tokens holding raw values flow into Semantic tokens which resolve differently in Light and Dark modes, then bind to Components</image:title>
      <image:caption>Layer 1 holds raw values (primitives). Layer 2 aliases them by UI role (semantics). Components only bind to Layer 2 - so a mode switch updates everything automatically.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-design-tokens-guide/</loc>
    <lastmod>2026-06-02</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-tokens-guide/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-tokens-guide/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-tokens-guide/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Figma-Design-Tokens-The-Complete-Guide-for-UI-UX-Designers-es.webp</image:loc>
      <image:title>Design Tokens y Variables de Figma: La Guía Completa (2026)</image:title>
      <image:caption>Guía 2026 de design tokens en Figma: Variables, primitivos, alias semánticos, dark mode, exportación DTCG y handoff CSS/TypeScript para equipos UI.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-tokens-two-layer-architecture.webp</image:loc>
      <image:title>Arquitectura de tokens de dos capas: los tokens Primitivos que guardan valores en bruto fluyen hacia tokens Semánticos que se resuelven de forma diferente en los modos Claro y Oscuro, luego se vinculan a los Componentes</image:title>
      <image:caption>La Capa 1 guarda valores en bruto (primitivas). La Capa 2 los alias por rol de interfaz (semánticas). Los componentes solo se vinculan a la Capa 2 - por lo que un cambio de modo actualiza todo automáticamente.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/blog/figma-design-system-best-practices/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-system-best-practices/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-system-best-practices/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-system-best-practices/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/Figma-Design-System-Best-Practices-for-UI-UX-Teams.webp</image:loc>
      <image:title>Figma Design System Best Practices (2026): Tokens, Sync &amp; Scale</image:title>
      <image:caption>Four decisions that separate scalable design systems from decaying ones: tokens first, one naming convention, a code sync pipeline, and a governance owner.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-ds-best-practices-pillars.webp</image:loc>
      <image:title>Five design system best practices: Tokens First, Named Owner, Code Sync, Living Docs, Ship Lean</image:title>
      <image:caption>Five habits that compound over time - Tokens First is the anchor, everything else depends on it.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://atomize.tools/es/blog/figma-design-system-best-practices/</loc>
    <lastmod>2026-05-12</lastmod>
    <priority>0.8</priority>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://atomize.tools/blog/figma-design-system-best-practices/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://atomize.tools/blog/figma-design-system-best-practices/"/>
    <xhtml:link rel="alternate" hreflang="es" href="https://atomize.tools/es/blog/figma-design-system-best-practices/"/>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/es/Figma-Design-System-Best-Practices-for-UI-UX-Teams-es.webp</image:loc>
      <image:title>Mejores Prácticas del Sistema de Diseño de Figma: Guía de Escalado para Equipos</image:title>
      <image:caption>Mejores prácticas para escalar un sistema de diseño en Figma: tokens, nomenclatura, accesibilidad, documentación, versionado y sincronización.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://cdn.atomize.tools/assets/en/figma-ds-best-practices-pillars.webp</image:loc>
      <image:title>Cinco mejores prácticas de sistemas de diseño: Tokens Primero, Propietario Nombrado, Sincronización de Código, Documentación Viva, Lanzar Reducido</image:title>
      <image:caption>Cinco hábitos que se acumulan con el tiempo - Tokens Primero es el ancla, todo lo demás depende de él.</image:caption>
    </image:image>
  </url>
</urlset>