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

Guides · Claude Code

Designing an app with Claude Code, from the prompt to the code

Updated November 18, 2026

Claude Code can design screens, not only build them: on a Saymock board, it draws them in HTML + Tailwind, checks them, takes your team’s comments and then implements what was approved. This guide follows one project from start to finish: an existing app that needs a new onboarding flow.

1. Connect Claude Code (two minutes)

In a terminal, install the plugin, then sign in from Claude Code:

claude plugin marketplace add saymock/claude-plugin && claude plugin install saymock@saymock

Run /mcp, choose saymock, then Authenticate: Saymock opens in the browser, you sign in (or create a free account) and approve. Start a new session so the tools load. The plugin brings the MCP server, four skills and the /saymock:session command. Other setups, the VS Code extension included: Claude Code setup.

2. Start from what is already built

A new flow should look like the rest of the app. Ask Claude Code to put the screens around it on the board first:

Put our current sign-in and home screens into Saymock from the code.

The plugin’s design-from-code skill reads your codebase for the real colors, fonts, icons and components (your Tailwind config, theme files, component library), takes screenshots of the running app when it can, and rebuilds the screens as editable frames. It then compares each frame with the screenshot (compare_to_reference) and fixes what differs. More: screens from your code.

3. Ask for the new flow

Design a three-screen onboarding for iPhone next to the home screen: welcome, pick your interests, turn on notifications. Same colors, fonts and tab bar as the app.

The saymock-design skill gives Claude Code a working method rather than a style:

  • It settles the system once (palette, type scale, spacing, radius) and reuses it.
  • It builds the first screen as the template of the others: shared blocks as components (status bar, header, tab bar), every list as a template with realistic data, never “Item 1, Item 2”.
  • It checks that screen with check_layout and get_screenshot before drawing the next ones, which inherit its components.
  • It lays the screens side by side in flow order, links them so the flow can be clicked through, and leaves a note beside a screen for what it cannot show (a rule, an edge case).

4. Compare directions

Propose three directions for the welcome screen: one minimal, one with an illustration, one with a short video.

Claude Code calls propose: the three options stay attached to the welcome screen, people preview each one in place, numbered with what it changes, and pick one. Nothing is scattered across the board. A bigger change you want to review before keeping it goes into a branch instead, merged from the app.

5. Review with your team, live

Share the board from the app: a link to view, comment or edit, no account needed to view. Then run, in Claude Code:

/saymock:session

Claude Code waits for comments addressed to it, on an element, marked for the agent or mentioning it. Each one is a task: it makes the change, checks it and answers in the thread, while people keep reviewing. The session stops by itself after a while without requests, or when someone presses End on the board.

6. Build what was approved

Implement the onboarding from Saymock in this project, with our existing components and routing.

The implement-design skill studies your codebase first, then gets the screens as code (export_code: React, Vue or HTML with the same Tailwind classes) or as specs for native apps (get_specs: an auto-layout tree with sizes, spacing, colors and text styles for SwiftUI, Compose, Flutter or React Native). It adapts them to your components and checks the result against the design. More: design to code.

Keeping it fast and cheap

  • One job per session. Everything an agent read earlier is re-read on each turn; a fresh session per flow keeps the context small (why it matters).
  • Edits, not rewrites. Ask for the change you want (“make the button full width”): Claude Code edits that element by its id instead of rewriting the screen.
  • Renders are counted. Screenshots, layout checks and comparisons run a browser; the Free plan includes 300 a month per workspace (limits). Editing tools are not counted.
  • Your tokens, your account. Saymock never calls a model and never bills your agent’s tokens; Claude Code runs on your Claude plan or API key.

Questions

Do I need the plugin, or is the MCP server enough?

The MCP server alone works: claude mcp add --scope user --transport http saymock https://app.saymock.com/mcp. The plugin adds the four skills (design from code, new designs, implementation, review) and the /saymock:session command.

Can Claude Code use my design system?

Yes. It reads your codebase for colors, fonts, icons and components, and can upload your fonts and logo to the workspace, so the screens use your real styles.

Does it work for native iOS and Android apps?

Yes. Screens are designed at device sizes (iPhone, Pixel, iPad…), and get_specs describes them for SwiftUI, UIKit, Compose, Views, Flutter or React Native.

How much does it cost?

Saymock bills human editors, never agents: the Free plan covers 2 editors per workspace with unlimited agents. Claude Code uses your own Claude plan or API key.

All the tools Claude Code gets: Saymock’s MCP tools. What the category is: design tools for AI agents.

See also

  • Figma MCP tokens
  • Design tools for agents
  • Figma import
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