# Bridging the gap between design and code with v0 By Steven Van · 2025-02-12 Speakeasy says v0 cut design-to-code translation, with Figma import and a custom Tailwind config, and a Terminal Preview concept built in a day. Speakeasy, which builds SDKs for developers, now uses [Vercel]()'s v0 to move from design to working code, according to a [Vercel customer story](). The team says it speeds up prototyping and cuts implementation time. Speakeasy follows a "design as code" approach. Figma is still used for early explorations, but static designs did not convey new ideas or win buy-in, and designing every feature in Figma was not practical. Some designs are imported from Figma into v0, while many start directly in v0. - The first concept for the Terminal Preview in the Speakeasy dashboard was built in a single day, leaving the team to refine interactions rather than translate static designs. - A custom Tailwind configuration in v0 defines fonts weights and colors to match their design system. - Designers and backend developers both use v0, and the team shares Loom recordings of v0 prototypes. "Share a v0" has replaced long Slack discussions and meetings. Design engineer Faraz Khan said he chose v0 for its "bias towards code", which meant less time redoing ideas in Figma and no time spent translating Figma to code before shipping. ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() [Original source]() [Read Bridging the gap between design and code with v0 on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-bridging-the-gap-between-design-and-code-with-v0