Wireframe Maker

Sketch → wireframe with Claude (the MCP recipe)

Turn a hand sketch, whiteboard photo, screenshot, or exported PDF page into an editable wireframe. Claude does the looking; the MCP server guarantees the result lands safely as a candidate version you review — master is never touched.

One-time setup

claude mcp add wireframes -- node /abs/path/to/scripts/mcp-server.mjs /abs/path/to/project.wfm.json

The server exposes read tools (list_screens, get_screen, render_screen, describe_control_type, …) and write tools that only ever create candidate versions (propose_screen, propose_edit, add_underlay, add_comment).

The recipe

Give Claude the image and this prompt shape:

Look at sketch.png. Recreate it as a wireframe screen in my project. 1. Call describe_control_type (no argument) to see the control vocabulary, then per-type for anything you use. 2. Call propose_screen with the traced controls — full props, real coordinates, canvas sized to the sketch. 3. Call add_underlay with image_path pointing at the sketch so I can review your trace against the source. 4. Call render_screen on your proposal, look at the SVG, and fix anything that doesn't match with propose_edit.

Claude sees the image directly (attach it or give a path it can read); the server never needs an API key and sends nothing anywhere.

What each step guarantees

StepToolGuarantee
Vocabularydescribe_control_typeExact property keys, enum values, defaults — no guessed prop names
Tracepropose_screenLands as a candidate version authored claude; carries full props; canvas set from the sketch
Source attachadd_underlayThe sketch ghosts at low opacity behind the proposal — in the app and in render_screen output, including when rendering the candidate version
Self-checkrender_screen → propose_editClaude inspects its own output and corrects before you ever look
Reviewthe app's compare view / review queueAccept promotes to master; reject discards; nothing automatic

PDFs

Drop the PDF straight into the app (the in-app PDF import): a page picker opens, and each selected page becomes a screen with the rendered page attached as a ghost underlay — no poppler, no dev machine; pdf.js loads lazily in the browser on first use. From there, trace over the underlay or run this recipe on the underlay image. One page often holds several phone frames — either trace them as one wide screen (the 2019 Pantry ground-truth screen is 3 iPhone frames, 248 controls on one canvas) or ask Claude for one propose_screen per frame.

Scale expectations

The pipeline is tested against the project's densest real screen: 248 controls of 10 types round-trip through propose_screen with every property intact (src/mcp/recipe.test.ts). Fidelity of the trace depends on the model and image quality; fidelity of the transport is guaranteed.

Out of scope (deliberately)

An in-app "convert with AI" button (BYO API key) is post-launch. This recipe needs only Claude Code / Claude Desktop and the MCP server above.