<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nadia Kim</title>
    <description>The latest articles on DEV Community by Nadia Kim (@nadia_kim).</description>
    <link>https://dev.to/nadia_kim</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4215025%2Fc157fded-e626-46d7-9dc0-86aaf5cf3a5e.jpg</url>
      <title>DEV Community: Nadia Kim</title>
      <link>https://dev.to/nadia_kim</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nadia_kim"/>
    <language>en</language>
    <item>
      <title>The design system is a contract, not a component library</title>
      <dc:creator>Nadia Kim</dc:creator>
      <pubDate>Sun, 01 Nov 2026 15:07:08 +0000</pubDate>
      <link>https://dev.to/nadia_kim/the-design-system-is-a-contract-not-a-component-library-49po</link>
      <guid>https://dev.to/nadia_kim/the-design-system-is-a-contract-not-a-component-library-49po</guid>
      <description>&lt;p&gt;The component library is the easy part. The contract is what makes a design system survive a team change.&lt;/p&gt;

&lt;p&gt;A contract here means: what the component accepts, what it promises, and what you'll never change without a major version.&lt;/p&gt;

&lt;p&gt;Practically:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Props are public API.&lt;/strong&gt; Rename one and you've broken someone's page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deprecation needs a date and a codemod&lt;/strong&gt;, not a note in a doc.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Docs are generated from the code&lt;/strong&gt;, because handwritten docs drift within a sprint.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Version the package&lt;/strong&gt;, even internally. "Just pull main" is how a design system becomes a fork.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The hard part is saying no. Every component request is a request to own another contract.&lt;/p&gt;

&lt;p&gt;The best design systems I've used felt small, and the docs explained the why, not just the props.&lt;/p&gt;

&lt;p&gt;Do you version your internal design system?&lt;/p&gt;

</description>
      <category>design</category>
      <category>frontend</category>
      <category>typescript</category>
    </item>
    <item>
      <title>Skeleton screens that don't shift the page</title>
      <dc:creator>Nadia Kim</dc:creator>
      <pubDate>Thu, 29 Oct 2026 10:36:57 +0000</pubDate>
      <link>https://dev.to/nadia_kim/skeleton-screens-that-dont-shift-the-page-4cg3</link>
      <guid>https://dev.to/nadia_kim/skeleton-screens-that-dont-shift-the-page-4cg3</guid>
      <description>&lt;p&gt;Every skeleton screen I've shipped has had the same bug: it doesn't match the real content's height, so the moment data arrives the page jumps.&lt;/p&gt;

&lt;p&gt;We fixed it by making the skeleton render the same layout boxes as the loaded state, with the text replaced by grey bars of the same line height. Sounds obvious, and it took three attempts because our components measured themselves after mount.&lt;/p&gt;

&lt;p&gt;Three rules we ended up with:&lt;/p&gt;

&lt;p&gt;The skeleton uses the same container, padding, and grid as the loaded state. No separate stylesheet.&lt;/p&gt;

&lt;p&gt;Fixed sizes for anything that can't shift (avatars, thumbnails), minimum heights for anything with variable text.&lt;/p&gt;

&lt;p&gt;Reserve space for the empty state too. An account with zero items should not move the footer.&lt;/p&gt;

&lt;p&gt;The win wasn't prettier loading. It was that scroll position survived a slow network, and the back button stopped landing people in the wrong place. Skeleton screens are a layout problem wearing a loading costume.&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>css</category>
      <category>ux</category>
    </item>
  </channel>
</rss>
