<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shyam Krishnan on Medium]]></title>
        <description><![CDATA[Stories by Shyam Krishnan on Medium]]></description>
        <link>https://medium.com/@shyam.ux?source=rss-80be9acfccaa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6J3O-tN39VgXmVj_3PpDFg.jpeg</url>
            <title>Stories by Shyam Krishnan on Medium</title>
            <link>https://medium.com/@shyam.ux?source=rss-80be9acfccaa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:35:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shyam.ux/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Vibe code your way to component library and design system- PART 1]]></title>
            <link>https://www.designsystemscollective.com/vibe-code-your-way-to-component-library-and-design-system-part-1-50b0a33a25a3?source=rss-80be9acfccaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/50b0a33a25a3</guid>
            <category><![CDATA[ui-development]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-engineering]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Shyam Krishnan]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 07:00:12 GMT</pubDate>
            <atom:updated>2026-07-06T06:24:27.240Z</atom:updated>
            <content:encoded><![CDATA[<p>The bottleneck that early-stage startups face when adopting a design thinking culture (which is primarily an iterative process) is in communicating and handing off assets to engineering. The problem is compounded by the fact that each team has its own technology stack. Hence, streamlining the process requires a surgical technique rather than a one-size-fits-all approach. I will break down, to the best of my ability, how you would navigate this maze.</p><h3>Audit the current interface.</h3><p>Take inventory of the current interfaces and UI components that are built. Group standard interfaces and define design constants based on the well-known atomic design principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h9ADk6oQ_urF87UIZChxvw.jpeg" /></figure><blockquote><strong>Atomic design is a methodology composed of five distinct stages working together to create interface design systems in a more deliberate and hierarchical manner.</strong></blockquote><p>The atoms of an interface are built using design constants, or as the community calls them, “design tokens.”. These include your font sizes, colour palettes, border radii, and more. You can learn more about the design system from Brad Frost&#39;s article <a href="https://atomicdesign.bradfrost.com/table-of-contents/">https://atomicdesign.bradfrost.com/table-of-contents/</a>.</p><h3>Built a component library using Figma.</h3><p>After you have identified and finalised your atomic design, start building it on Figma.</p><h4>Component list</h4><p><strong>Template level</strong> | Navigation, header, report view, dashboard view, settings view</p><p><strong>Molecules level</strong> |<strong> </strong>menu list, tabbed view, detail view (overlay panel), search box,</p><p><strong>Atom level</strong> | Button, drop-down, layout grid, model box, multi-select input, form input fields, radio button, checkbox, etc.</p><p><strong>Design Tokens</strong> | colour palette values (default, dark), padding values, margin values, shadow value</p><p>Convert your components and design tokens to the UI component of your choice.</p><h3>Figma File to UI component.</h3><p>The best way to do this in the AI Era is to partner with AI tools like <strong>V0.app</strong> and <strong>Bolt.new</strong>, <strong>Lovable.dev</strong> or even <strong>cursor</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7mZaaRX9pNa5CNploh5wcg.png" /></figure><p>ShadCN is the best component library to work with AI tools (Since they are built on top of ShadCN)</p><h3>Step 1: Enable Figma MCP</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDCtnEeA5K6WVYV4YPDrfg.png" /></figure><p>This allows tools like Cursor and VS Code to communicate with Figma, including its frames and components.</p><h3>Step 2: Open the cursor app to build a storybook environment for the components</h3><h4>Option 1</h4><blockquote>Prompt: <br>As a UX engineer, set up a storybook.js environment based on the framework and environment:<br>1. Next.js ≥ 14.1<br>2. Tailwind: 3.4.7<br>3. Shadcn/UI</blockquote><h4>Option 2</h4><p>Follow the step-by-step instructions from the article below on the preferred IDE of your choice (i.e: Cursor, VSCode)</p><p><a href="https://blog.logrocket.com/building-next-js-app-tailwind-storybook/">https://blog.logrocket.com/building-next-js-app-tailwind-storybook/</a></p><h3>Step 3: Map Figma variable with ShadCN variables</h3><ol><li>Create a base Tailwind theme with <a href="https://tweakcn.com/editor/theme"><strong>TweakCN</strong></a> (you can adjust it later in Figma).</li><li>Copy the theme code.</li><li>Install the <a href="https://www.figma.com/community/plugin/1463378448591477945"><strong>Tailwind CSS v4 Variables Figma</strong></a> plugin.</li><li>Paste the code into the text window and name your collection.</li><li>Click <strong>Local Variables</strong>.</li><li>The <strong>ShadCN theme variable</strong> is now in Figma.</li><li>Map your internal variable values to the <strong>ShadCN theme variables</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qeZ-jdedVRFJIJ71VwFHqw.png" /></figure><p>8. Use the <strong>Figma to Tailwind CSS</strong> plugin to generate <strong>global.css/index.css </strong>file along with<strong> a Tailwind.config file</strong> to be added to the storybook setup code base.</p><h3>Step 4: Build the Selected Figma Component using Cursor or VSCode</h3><ol><li>While making sure that the component is selected in Figma type the prompt that goes like</li></ol><blockquote>Prompt: <br>Using ShadCN {SHADCN_EQUVALENT_COMPONENT_NAME} (Ex: Toast is called Sonnar in ShadCN) create the selected Figma component and make sure to generate Story component for the same</blockquote><h3>🎉 Congratulation you have taken the first step in building your own design system that a developer would approve</h3><p>I will be diving deeper in Part 2…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50b0a33a25a3" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/vibe-code-your-way-to-component-library-and-design-system-part-1-50b0a33a25a3">Vibe code your way to component library and design system- PART 1</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why the most preferred color by everyone is rare in nature.]]></title>
            <link>https://medium.com/@shyam.ux/why-the-most-preferred-color-by-everyone-is-rare-in-nature-7fe271a590d2?source=rss-80be9acfccaa------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fe271a590d2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[bioengineering]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[nature]]></category>
            <dc:creator><![CDATA[Shyam Krishnan]]></dc:creator>
            <pubDate>Mon, 06 Sep 2021 08:09:13 GMT</pubDate>
            <atom:updated>2022-02-04T02:35:10.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*Omkumci69EPL8m9v" /><figcaption>Blue Morpho butterfly. (Photo Credit: Didier Descouens / Wikimedia Commons)</figcaption></figure><p>Yes! we are talking about the color blue. But how is this true if we see blue everywhere and that is the underlying reason why the preferred color is mostly blue.</p><p>Although we see blue in nature, blue pigmentation in nature is rare and there are few animal and plant life that have their own blue pigment. The rest of the animals and plants create blue color through tiny variation and bumps in their skin/feathers etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/0*s0_HcWbEPZzK7sux.png" /><figcaption>Photo Credit: <a href="https://www.researchgate.net/figure/Morphologies-and-structures-of-the-Morpho-butterfly-wing-before-and-after-selective_fig2_327734152">https://www.researchgate.net</a></figcaption></figure><p>The structure bounces other color wavelengths at different angles and direction but amplifies the blue wavelength as they reflect away from the structure the wavelengths are in-phase. This is the reason why in some angles the butterfly wing generate a iridium Blue shade.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q1LfW5Ijd-cQ2KzV-vhP8g.png" /></figure><blockquote>“Solving a biology problem with physics”</blockquote><p>No one know the exact reason why nature wanted some species to have blue hue as part of their body, but we all can agree that nature took <strong>the most cost efficient path to solving this problem</strong> as changing the chemistry of a species body is much difficult than iteratively changing the structure.</p><h3><strong>Key Take-Away For Designers</strong></h3><p>Always assess the outcome of solving the problem and device a solution for the outcome, this way you avoid wasting time and resources on building a solution that could have been solved with much less effort.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fe271a590d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>