stitch::code-to-design — Claude Code skill for Stitch
Moves an existing frontend into Stitch by extracting standalone HTML and a design system, then uploading both to a project. Useful when bringing pages or components into Stitch for further work.
npx skills add google-labs-code/stitch-skills --skill stitch::code-to-design -a claude-code
npx skills add google-labs-code/stitch-skills --skill code-to-design -a claude-codeWhat stitch::code-to-design does
The skill runs a three-part workflow: extract standalone HTML, analyze project files to create .stitch/DESIGN.md, then upload both results to Stitch. Supported source examples include React, Next.js, Angular, and Vue.
You need a running local dev server or a built directory with index.html and assets, plus the Stitch projectId and an API key. Without a server or built output, there is no page to extract. Browser review of the extracted file is optional and does not block the next step.
HTML and the design system are uploaded separately. The HTML upload uses the page route as its title, such as /dashboard. The workflow delegates extraction, design analysis, and uploads to other Stitch skills, so those skills need to be available in your environment.
What it helps with
- move an existing frontend page into Stitch
- extract standalone HTML from a build or local dev server
- create DESIGN.md from project components and styles
- upload HTML and a design system to a Stitch project
Example prompts for the agent
- Move the `/dashboard` page from this React project into Stitch.
- Extract standalone HTML from the running app and upload it to my Stitch project.
- Analyze the components and styles, create `.stitch/DESIGN.md`, and upload the design system to Stitch.
How to install stitch::code-to-design
1Skills CLI (Vercel)
npx skills add google-labs-code/stitch-skills --skill stitch::code-to-design -a claude-codenpx skills add google-labs-code/stitch-skills --skill code-to-design -a claude-code2Manually: put the files in place
~/.claude/skills/code-to-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-to-design/
1Skills CLI (Vercel)
npx skills add google-labs-code/stitch-skills --skill code-to-design -a codex2Manually: put the files in place
.agents/skills/code-to-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add google-labs-code/stitch-skills --skill code-to-design -a cursor2Manually: put the files in place
.cursor/skills/code-to-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install google-labs-code/stitch-skills code-to-design2Manually: put the files in place
.github/skills/code-to-design/SKILL.md1Skills CLI (Vercel)
npx skills add google-labs-code/stitch-skills --skill code-to-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/google-labs-code/stitch-skills --path plugins/stitch-design/skills/code-to-designManually: put the files in place
.devin/skills/code-to-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add google-labs-code/stitch-skills --skill code-to-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set15
The whole set →Similar
Questions about stitch::code-to-design
How do I install stitch::code-to-design in Claude Code?
Run npx skills add google-labs-code/stitch-skills --skill stitch::code-to-design -a claude-code. An alternative is npx skills add google-labs-code/stitch-skills --skill code-to-design -a claude-code.
What does stitch::code-to-design do?
It extracts standalone HTML from an existing frontend, creates .stitch/DESIGN.md from the project source, and uploads both to Stitch.
What do I need before moving a project to Stitch?
Have a running local dev server or a built directory containing index.html and assets, the Stitch projectId, and an API key. The workflow also relies on other Stitch skills for extraction and uploads.
Source text
SKILL.md · Apache-2.0
--- name: stitch::code-to-design description: >- Convert frontend code (Vite, React, Angular, Vue, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React/Angular/Vue components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked. allowed-tools: - "stitch*:*" - "Bash" - "Read" - "Write" - "web_fetch" --- # 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](../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](../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](../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](../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.
© google-labs-code · Apache-2.0 · google-labs-code/stitch-skills