Skip to content
saymock
Product Agents Use cases Developers FAQ Pricing
EN, English
  • Français
  • English
  • Deutsch
  • Español
  • Português
  • Italiano
  • Nederlands
  • 日本語
  • 한국어
  • 简体中文
Theme
Sign in Try it

Use cases · Screens from code

Your app’s screens, redrawn from its code

Updated November 18, 2026

Most apps have no up-to-date design file: the code is the truth. Your coding agent reads it and rebuilds the screens on a Saymock board, with the project’s real colors, fonts, icons and components. You get a design file of what is built, to discuss, annotate and redesign from.

Create a free account Get the Claude Code plugin

How it goes

  1. Agree on the scope. A route, a flow (sign-up → onboarding → home) or the main screens, with the device for each. A small complete flow beats many half-done screens.
  2. The agent collects your design system. Colors, radii and spacing from your Tailwind theme or CSS variables, font families, your icon library, logos and images uploaded as files, and shared blocks (header, sidebar, tab bar) as Saymock components.
  3. Screenshots of the running app, when it runs. The agent captures each screen at the target size and uploads it as a reference.
  4. It builds and measures. One frame per screen, real copy from your code or translation files, blocks named after your components. compare_to_reference scores each frame against the app’s screenshot and names what differs; the agent fixes and compares again.
  5. A note says where it comes from: routes, commit, and what was approximated.

In Claude Code, the plugin’s design-from-code skill runs these steps. Other coding agents (Cursor, Codex, Copilot, Gemini CLI) have the same tools: ask them in these words.

Prompts that work

Put our sign-up flow into Saymock from the code: the three screens on iPhone 16, with our Tailwind colors and Lucide icons. Compare each with a screenshot of the dev server.

Recreate the settings page from this repository in Saymock, then propose two clearer layouts next to it.

What it is good for

  • Redesigns that start from the real product, not from memory.
  • Reviews with people who do not read code: they comment on screens.
  • Documentation of what shipped, with the components named as in the code.
  • A round trip: once the redesign is approved, design to code brings it back into the project.

Questions

Does my code leave my machine?

Your agent reads the code where it runs and sends Saymock only the screens it draws (HTML), plus the images and fonts it uploads. Saymock never receives your repository.

Which stacks does it work with?

Web codebases: Tailwind classes carry over directly, other styles are translated into Tailwind values (CSS variables, token files, theme configs). For an app whose code the agent cannot translate, it can rebuild the screens from screenshots and measure them the same way.

How faithful is the result?

When the app runs, it is measured: each frame is compared with a screenshot of the real screen, and the agent fixes the elements that differ most.

Related: design review, Saymock for Cursor, for Codex, the benchmark (reproducing screens, measured).

See also

  • Mobile apps
  • Wireframes
  • Landing pages
  • Design to code
  • Design review
saymock
Product Agents Developers FAQ Pricing Benchmark Figma MCP alternative Connect your agent Use cases Gallery Guides MCP tools Changelog About Contact Sign in

© 2026 Saymock

Legal notice Terms of use Terms of sale Privacy