# FT Design System
> Design infrastructure for humans, engineers, and AI agents
- Role: Design System Architect & Sole Developer
- Company: Freight Tiger
- Timeline: 2025 - 2026
Content
## Links
<div class="case-study-link-list">
<a class="case-study-link-list__item" href="https://ftdesignsystem.netlify.app" target="_blank" rel="noopener noreferrer">
<span class="case-study-link-list__icon" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<circle cx="12" cy="12" r="9"></circle>
<path d="M3 12h18"></path>
<path d="M12 3a14.5 14.5 0 0 1 0 18"></path>
<path d="M12 3a14.5 14.5 0 0 0 0 18"></path>
</svg>
</span>
<span>Live View</span>
<span class="case-study-link-list__arrow" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<path d="M7 17L17 7"></path>
<path d="M9 7h8v8"></path>
</svg>
</span>
</a>
<a class="case-study-link-list__item" href="https://www.npmjs.com/package/ft-design-system" target="_blank" rel="noopener noreferrer">
<span class="case-study-link-list__icon" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="currentColor">
<path d="M3 7.5h18v9H12v-6H9v6H3z"></path>
</svg>
</span>
<span>npm Package</span>
<span class="case-study-link-list__arrow" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<path d="M7 17L17 7"></path>
<path d="M9 7h8v8"></path>
</svg>
</span>
</a>
<a class="case-study-link-list__item" href="https://ftdesignsystem.netlify.app/docs/ai-prompts" target="_blank" rel="noopener noreferrer">
<span class="case-study-link-list__icon" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<path d="M12 3v3"></path>
<path d="M12 18v3"></path>
<path d="M3 12h3"></path>
<path d="M18 12h3"></path>
<path d="m5.6 5.6 2.1 2.1"></path>
<path d="m16.3 16.3 2.1 2.1"></path>
<path d="m18.4 5.6-2.1 2.1"></path>
<path d="m7.7 16.3-2.1 2.1"></path>
<circle cx="12" cy="12" r="3"></circle>
</svg>
</span>
<span>AI Prompts</span>
<span class="case-study-link-list__arrow" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<path d="M7 17L17 7"></path>
<path d="M9 7h8v8"></path>
</svg>
</span>
</a>
<a class="case-study-link-list__item" href="https://github.com/chetanft/components" target="_blank" rel="noopener noreferrer">
<span class="case-study-link-list__icon" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="currentColor">
<path d="M12 2C6.48 2 2 6.58 2 12.22c0 4.5 2.87 8.3 6.84 9.64.5.1.68-.22.68-.49 0-.24-.01-1.03-.01-1.87-2.78.62-3.37-1.2-3.37-1.2-.46-1.18-1.11-1.5-1.11-1.5-.91-.64.07-.63.07-.63 1 .07 1.53 1.06 1.53 1.06.9 1.56 2.35 1.11 2.92.85.09-.67.35-1.11.63-1.37-2.22-.26-4.55-1.14-4.55-5.09 0-1.12.39-2.03 1.03-2.75-.1-.26-.45-1.31.1-2.73 0 0 .84-.28 2.75 1.05A9.3 9.3 0 0 1 12 6.91c.85 0 1.7.12 2.5.35 1.9-1.33 2.74-1.05 2.74-1.05.56 1.42.21 2.47.11 2.73.64.72 1.03 1.63 1.03 2.75 0 3.96-2.33 4.82-4.56 5.08.36.32.68.95.68 1.92 0 1.39-.01 2.5-.01 2.84 0 .27.18.59.69.49A10.22 10.22 0 0 0 22 12.22C22 6.58 17.52 2 12 2z"></path>
</svg>
</span>
<span>GitHub Repo</span>
<span class="case-study-link-list__arrow" aria-hidden="true">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<path d="M7 17L17 7"></path>
<path d="M9 7h8v8"></path>
</svg>
</span>
</a>
</div>
## It started in Figma
- I started by creating reusable Figma components for Freight Tiger’s product designs, including buttons, tables, checkboxes, and badges.
- I turned those components into a design system developers could follow. The goal was to cut development time by giving engineers a pattern to reuse each time they built a new screen.
- I moved the component examples into Storybook so developers could see how each component looked and behaved in code.
## From Storybook to npm and the web
- As AI tools made it easier to generate interfaces, I published the React components to npm and built a documentation site. Developers could install the library and find examples of how to use it.
- Grew the library to **134+ React components and 194 custom icons**, including navigation, file uploads, and charts.
## Helping PMs get better prototypes
- I noticed PMs could generate prototypes quickly with Lovable, but the screens often used components and styles that didn’t match Freight Tiger’s product.
- I wrote reusable AI prompts that guided Lovable toward the existing library. I also built a machine-readable registry so AI tools could find supported components, variants, and examples.
- PMs could use those prompts to prototype with the same components engineers could import into the product.
## What I’d do earlier
- Define theme tokens before scaling the library to avoid replacing hardcoded styles later.
- Adopt Radix from the start so keyboard and focus behavior are built in as components are added.
## Related Links
- Live Product: https://ftdesignsystem.netlify.app
- npm Package: https://www.npmjs.com/package/ft-design-system## Navigation
- Previous: PTL Module Design (https://chetank.vercel.app/work/ptl-module-design)