Use cases · Design to code
From approved screens to code in your project
Updated
Screens on a Saymock board are already HTML + Tailwind, so there is no translation from vectors to guess. Your coding agent reads the approved screens, exports them or reads their specs, then builds them with your project’s own components, tokens and routing.
How it goes
- Point the agent at the design. Paste the file link or name the screens. It looks at each one first, and reads the notes and open comments beside them: they often carry decisions.
- It studies your codebase. Framework, Tailwind version and theme, UI components, icons, routing, translation files: the export is mapped onto them, not pasted next to them.
-
Web:
export_code. React (TSX), Vue or standalone HTML, one file per screen and per component with typed props, repeated rows as a data array and a loop, icons as imports. -
Native or any stack:
get_specs. An auto-layout tree with measured spacing and sizes in points or dp, colors and text styles, icons with SF Symbol and Material Symbol equivalents, lists, components, states and navigation. -
Adapt and verify. Raw buttons become your
<Button>, colors become your tokens. The agent runs the app, compares the result with the design, then runs your lint and tests.
In Claude Code, the plugin’s implement-design skill runs these steps.
Cursor, Codex, Copilot and Gemini CLI use the same tools.
Prompts that work
Implement the “Invite teammates” screen from this Saymock file in our React app, with our components in src/components/ui.
Build the onboarding flow from Saymock in SwiftUI, using get_specs, with our existing colors and fonts.
Questions
Which frameworks can it export?
export_code gives React, Vue or HTML. For Svelte, Astro, server templates or native apps, the agent translates the HTML export or works from get_specs.
We are on Tailwind v3.
Designs use Tailwind v4 utilities; the few that differ in v3 are translated by the agent (for example gradients and CSS-variable sizes).
What if the design has a problem?
The agent says so, or leaves a comment on the element, rather than silently diverging from the screen.
Related: screens from code (the other way), Saymock for Cursor, for VS Code, Saymock vs Figma MCP.