<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design Systems on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/design-systems/</link><description>Recent content in Design Systems on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 01 Jun 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/design-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Product Thinking (3): UX &amp; Design Systems — Tokens, Dark Mode, and Bilingual</title><link>https://www.chenk.top/en/product-thinking/03-ux-design/</link><pubDate>Mon, 01 Jun 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/product-thinking/03-ux-design/</guid><description>&lt;h2 id="the-problem-with-just-make-it-look-good" class="heading-anchor">The Problem With &amp;ldquo;Just Make It Look Good&amp;rdquo;&lt;a href="#the-problem-with-just-make-it-look-good" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Every engineer who has ever touched CSS knows the feeling: you open a stylesheet written six months ago and find forty-seven shades of grey, twelve font sizes that follow no discernible scale, and a dark mode implementation consisting of &lt;code>filter: invert(1)&lt;/code> on the body element. The code works. The site renders. But every new feature requires archaeology — digging through layers of ad-hoc decisions to figure out what the &amp;ldquo;right&amp;rdquo; shade of muted text is supposed to be.&lt;/p></description></item></channel></rss>