#164 How Fin (Intercom) Prototypes With AI with Domingo Widen

<p>Domingo Widen is a Staff Product Designer at Fin (formerly Intercom), where he leads the Frontend Infrastructure team — the team that builds the tools, design system and AI setup everyone else uses to ship. In this episode he opens up his actual workflow: a &quot;Design Playground&quot; repo every designer, PM and researcher can clone, prototyping directly in production, and &quot;Search Intelligence&quot; a persistent knowledge layer that teaches Claude how Fin designs and codes.</p><p>We talk about what happens when the Figma file stops being the deliverable: how a complex filtering system got built as a working prototype instead of ten mockups, how handoff turns into a PR plus an auto-generated spec, and why engineers ended up being the biggest users of the design team&#39;s skills. If you want a concrete, unhyped look at what an AI-native design team actually does day to day, this one is for you.</p><p><br></p><p><strong>Key Learnings</strong></p><ul><li><strong>There are two modes of AI prototyping and you need both.</strong> </li><li><strong>The design system is the guardrail that makes this safe.</strong> Because everyone builds on the same components and tokens, a PM or researcher can prototype without producing something off-brand or unusable.</li><li><strong>Skills are only as good as the information behind them.</strong> Fin&#39;s early skills gave mixed results — so they built &quot;Search Intelligence&quot;, a persistent information layer that every skill reads from. </li><li><strong>Handoff becomes a PR + a generated spec.</strong> A &quot;Search Handoff&quot; skill reads the prototype code and writes the doc: architecture, what was built, which workarounds were needed, what broke. The engineer picks it up from there and focuses on plumbing, data and edge cases.</li></ul><ul><li><strong>The biggest users of the design team&#39;s skills are engineers.</strong> </li><li><strong>Everyone works in the same medium now.</strong> PM, designer and engineer used to live in Google Docs, Figma and VS Code. Now it&#39;s one shared artifact — which makes conversations concrete but also creates an identity crisis for designers who defined their value by the file.</li><li><strong>Curiosity + critical thinking are the two traits that survive.</strong></li><li><strong>Play is back — and it counts.</strong> Side projects (a baby sleep tracker, a garden planner that checks on tomatoes) are now part of a portfolio.</li></ul><p><br></p><p><strong>Domingo Widen