mcpField
S
stitch::code-to-design

stitch::code-to-design

github.com/google-labs-codeDesign & UI8.6k10.3k installsUpdated 10w ago
Repository

About stitch::code-to-design

A workflow skill that converts an existing frontend into a Stitch design by coordinating HTML extraction, design-system documentation, and uploads. It is intended for teams iterating on existing React, Vue, Angular, or other frontend applications in Stitch.

Key features

  1. 01Coordinate three conversion skills
  2. 02Extract self-contained HTML
  3. 03Generate a design-system document
  4. 04Upload design system and page HTML
  5. 05Label screens by route

Use cases

  1. 01Bring a running frontend page into Stitch
  2. 02Convert a built web app for design iteration
  3. 03Upload route-specific screens with design documentation

MCP support

Uses Stitch MCP to locate the target project; the workflow also delegates design-system creation and upload tasks to the related skills.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/google-labs-code/stitch-skills --skill stitch::code-to-design

After installing, type/stitch::code-to-designin Claude Code to confirm it loaded.

Details

From the project README

Code to Design

Transform your existing frontend code (React + Vite, Next.js, Angular, Vue, etc.) into a Stitch Design so you can iterate and improve it using Stitch.

This skill orchestrates three other skills in sequence:

  1. extract-static-html: Extract a single self-contained HTML file from your build output or running dev server (e.g., Vite dev server or Angular CLI ng serve).
  2. extract-design-md: Analyze the source code (including Angular angular.json, external .html templates, theme files, and components) to create a design system (DESIGN.md).
  3. upload-to-stitch: Upload that HTML file and the design system to your Stitch project.

Workflow

Follow these steps to convert your existing code.

Prerequisites
  • A running local dev server (e.g. npm run dev, ng serve) OR a built web application directory containing index.html and assets.
  • Target Stitch projectId (use list_projects if unknown).
Steps
1. Extract Self-Contained HTML

Delegate to the extract-static-html skill to generate a standalone HTML file. Read skills/extract-static-html/SKILL.md for detailed instructions and script usage.

Expected output: A single file like /path/to/extracted/standalone.html.

2. Verify HTML (Optional — User-Driven)

After extraction, inform the user of the output file path so they can manually verify in a browser if desired. Do not block on verification — proceed directly to Step 3.

If the user reports issues after reviewing, fix them before continuing.

3. Extract Design System (File)

Delegate to the extract-design-md skill to analyze the project's source files (components, stylesheets, theme configs) and produce a design system. Read skills/extract-design-md/SKILL.md for the full analysis workflow.

Write .stitch/DESIGN.md following the extract-design-md skill's output structure.

4. Upload DESIGN.md and Create Design System in Stitch

Delegate to the manage-design-system skill to upload the DESIGN.md and create the design system in Stitch. Read skills/manage-design-system/SKILL.md for the full workflow (upload script usage, create_design_system_from_design_md call, and required schemas). Pass --generated-by 'stitch::code-to-design' when uploading.

5. Upload HTML to Stitch

Use the same upload-to-stitch skill's script to upload the extracted HTML file. Read skills/upload-to-stitch/SKILL.md for detailed instructions and script usage.

You will need:

  • The path to the standalone HTML file generated in Step 1.
  • Your Stitch API Key (same key used in Step 4).
  • The target projectId.
  • The --generated-by argument set to 'stitch::extract-static-html'.
  • The --title argument set to the route path of the page (e.g., '/dashboard', '/settings/profile', '/inbox') so that the screen name/title in Stitch clearly identifies its route in the application.

Comments

Markdown supported