https://atomize.tools/ 2026-05-06 1.0 weekly https://atomize.tools/blog 2026-05-06 0.9 weekly https://atomize.tools/author/vitalina-makus 2026-05-06 0.75 monthly https://atomize.tools/blog/find-untokenized-values-figma 2026-05-06 0.8 monthly https://atomize.tools/blog/find-untokenized-values.webp Atomize Find Untokenized Values panel 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. https://atomize.tools/blog/design-system 2026-04-27 0.8 monthly https://atomize.tools/blog/ds-four-layers.webp Design system four-layer architecture The four layers of a design system - each layer depends on the one below it. https://atomize.tools/blog/ds-token-architecture.webp Design token primitive vs semantic architecture Primitive tokens hold raw values; semantic tokens alias primitives and resolve differently per mode. Components bind to semantic tokens - never to primitives directly. https://atomize.tools/blog/figma-vs-pencil-design-system 2026-04-26 0.8 monthly https://atomize.tools/blog/figma-vs-pencil-comparison.webp Figma vs Pencil design system comparison Different strengths, often used together - Figma owns design and collaboration, Pencil owns the design-to-code pipeline. https://atomize.tools/blog/figma-variables-dark-mode 2026-04-26 0.8 monthly https://atomize.tools/blog/figma-dark-mode-variables-comparison.webp Figma light vs dark mode variables comparison Same semantic token names, different values per mode. Switch mode in Figma and all components update automatically. https://atomize.tools/blog/figma-design-system-best-practices 2026-04-20 0.8 monthly https://atomize.tools/blog/figma-ds-best-practices-pillars.webp Five Figma design system best practice pillars Five habits that compound over time - Tokens First is the anchor, everything else depends on it. https://atomize.tools/blog/figma-design-tokens-guide 2026-04-20 0.8 monthly https://atomize.tools/blog/figma-tokens-two-layer-architecture.webp Figma tokens two-layer architecture 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. https://atomize.tools/blog/figma-plugins-design-system-token-workflows 2026-04-20 0.8 monthly https://atomize.tools/blog/figma-plugins-categories.webp Six categories of Figma design system plugins Design system plugin work splits into six distinct categories - each solves a different part of the token and component pipeline. https://atomize.tools/blog/how-to-build-design-system-figma 2026-04-20 0.8 monthly https://atomize.tools/blog/figma-ds-build-process-phases.webp Three-phase Figma design system build process Three phases to a production design system - Foundation first, then Components, then Governance. Each phase builds on the last. https://atomize.tools/blog/what-is-design-system-figma 2026-04-20 0.8 monthly https://atomize.tools/blog/what-is-ds-four-components.webp Four components of a Figma design system Every mature design system has four layers - each adds more value and more maintenance responsibility. https://atomize.tools/blog/figma-design-system-parity-code-sync 2026-04-17 0.8 monthly https://atomize.tools/blog/figma-ds-token-sync-pipeline.webp Figma to code token sync pipeline 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. https://atomize.tools/privacy 2026-05-06 0.6 monthly