Layovelle

Design-to-Code Workflow

Documentation

Legacy. This section documents the original Layovelle MCP server at mcp.moda.app/mcp, built around start_design_task and get_moda_canvas. It is superseded by Layovelle for Agents — the moda CLI wherever your agent has a shell, and the Layovelle connector for claude.ai and other chat hosts. The connector replaces this server, so the tools below retire with it. These pages stay published for existing integrations; start new ones on Layovelle for Agents.
This guide covers the recommended workflow for converting Layovelle designs to production code using the MCP server and an AI coding agent.

The basic workflow

Design in Layovelle

Create your UI design on the Layovelle canvas.

Share

Generate a public share link (or use the private canvas URL with auth).

Prompt

Paste the link in your editor and tell the agent what to build.

Review

Check the generated code and iterate.

Writing effective prompts

The quality of generated code depends heavily on your prompt. Be specific about:

Framework and language

Component structure

Responsive behavior

Multi-page designs

For slide decks or multi-page canvases, the agent can work through pages sequentially:
The agent will call list_moda_canvas_pages to discover the pages, then fetch each one with get_moda_canvas.

Generating theme files

If you already have a component library and just need design tokens:
The agent will use get_moda_canvas_tokens to extract colors, fonts, and spacing.

Tips for better results

Name your layers

The MCP server’s transformer uses layer names to determine semantic meaning. A layer named cta-button produces a Button tag; an unnamed rectangle might be interpreted as a Box. See Naming Layers for the full keyword reference.

Use design variables

Colors and values defined as Layovelle variables appear in the design tokens output with their names, making it easier for the agent to create meaningful CSS custom properties or theme tokens.

Keep designs clean

Use exports for complex layouts

When the pseudo-HTML alone doesn’t capture the visual intent, the agent can export a visual reference with export_canvas (use png format for design-to-code). This is especially useful for:

Common patterns

Design system from canvas

Pixel-perfect implementation

Component library