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:
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).
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).
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 stitch-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
stitch-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
stitch-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 stitch-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.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/stitch-code-to-design and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Stitch MCP
- Fallback prompt: "Use the Code to Design skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use local
.stitch/ artifacts, exported HTML or screenshots, bundled scripts, and the Stitch web UI when the host does not expose the needed Stitch MCP operation.
- Do not claim screen lookup, generation, editing, or variant MCP calls unless those tools are present in the active host tool list.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Claiming a Stitch screen-generation, screen-editing, or screen-retrieval MCP call succeeded when the active host does not expose that tool.
- Uploading files, screenshots, HTML, markdown, or design assets to Stitch without user-approved destination and artifact details.
- Reading, printing, storing, or committing Stitch API keys, MCP config secrets, cookies, or credential-bearing files.
- Treating generated design or code as final without local render, syntax, or artifact verification.
- Collapsing this workflow into a broader frontend/design skill when Stitch-specific files, project IDs, or design-system assets matter.
Verification Protocol
Before claiming this skill was applied successfully:
- Pass/fail:
.stitch/DESIGN.md exists and summarizes real source tokens.
- Pass/fail: The static HTML opens locally enough to inspect core layout and images.
- Pass/fail: Stitch design-system creation was MCP-verified or the fallback evidence is recorded.
- Pass/fail: No API key, token, cookie, or credential-bearing config was copied into durable files.
- Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable.
- Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior.
Related Skills
1---
2name: stitch-code-to-design
3version: "2.0"
4last_updated: 2026-09-08
5tags: [stitch, design, frontend, html, migration]
6description: "Convert an existing frontend into Stitch-ready design assets by extracting static HTML, writing DESIGN.md, creating the design system, and uploading approved files."
7license: "Apache-2.0"
8metadata:
9 source: https://skillmd.com/skills/practicalswan/stitch-code-to-design
10---
11
12# Code to Design
13
14Transform your existing frontend code (React + Vite, Next.js, Angular, Vue, etc.) into a Stitch Design so you can iterate and improve it using Stitch.
15
16This skill orchestrates three other skills in sequence:
171. `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`).
182. `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).
193. `upload-to-stitch`: Upload that HTML file and the design system to your Stitch project.
20
21## Workflow
22
23Follow these steps to convert your existing code.
24
25### Prerequisites
26
27- A running local dev server (e.g. `npm run dev`, `ng serve`) OR a built web application directory containing `index.html` and assets.
28- Target Stitch `projectId` (use `list_projects` if unknown).
29
30### Steps
31
32#### 1. Extract Self-Contained HTML
33
34Delegate to the `extract-static-html` skill to generate a standalone HTML file.
35Read [stitch-extract-static-html/SKILL.md](../stitch-extract-static-html/SKILL.md) for detailed instructions and script usage.
36
37Expected output: A single file like `/path/to/extracted/standalone.html`.
38
39#### 2. Verify HTML (Optional — User-Driven)
40
41After extraction, inform the user of the output file path so they can manually
42verify in a browser if desired. **Do not block on verification** — proceed
43directly to Step 3.
44
45If the user reports issues after reviewing, fix them before continuing.
46
47#### 3. Extract Design System (File)
48
49Delegate to the `extract-design-md` skill to analyze the project's source files
50(components, stylesheets, theme configs) and produce a design system. Read
51[stitch-extract-design-md/SKILL.md](../stitch-extract-design-md/SKILL.md) for the
52full analysis workflow.
53
54Write `.stitch/DESIGN.md` following the `extract-design-md` skill's output
55structure.
56
57#### 4. Upload DESIGN.md and Create Design System in Stitch
58
59Delegate to the `manage-design-system` skill to upload the `DESIGN.md` and
60create the design system in Stitch. Read
61[stitch-manage-design-system/SKILL.md](../stitch-manage-design-system/SKILL.md) for
62the full workflow (upload script usage, `create_design_system_from_design_md`
63call, and required schemas). Pass
64`--generated-by 'stitch::code-to-design'` when uploading.
65
66#### 5. Upload HTML to Stitch
67
68Use the same `upload-to-stitch` skill's script to upload the extracted HTML file.
69Read [stitch-upload-to-stitch/SKILL.md](../stitch-upload-to-stitch/SKILL.md) for detailed instructions and script usage.
70
71You will need:
72- The path to the standalone HTML file generated in Step 1.
73- Your Stitch API Key (same key used in Step 4).
74- The target `projectId`.
75- The `--generated-by` argument set to `'stitch::extract-static-html'`.
76- 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.
77
78<!-- MCP:START -->
79
80<!-- PORTABILITY:START -->
81## Cross-Client Portability
82
83This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
84
85- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
86 workflow in project instructions when folder discovery is unavailable.
87- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
88- Codex: install or sync the folder into
89 `$CODEX_HOME/skills/stitch-code-to-design` and restart Codex after major changes.
90
91<!-- PORTABILITY:END -->
92
93## MCP Availability And Fallback
94
95Preferred MCP Server: Stitch MCP
96
97- Fallback prompt: "Use the Code to Design skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
98- Use local `.stitch/` artifacts, exported HTML or screenshots, bundled scripts, and the Stitch web UI when the host does not expose the needed Stitch MCP operation.
99- Do not claim screen lookup, generation, editing, or variant MCP calls unless those tools are present in the active host tool list.
100- Do not claim an MCP operation was used when the active host does not expose it.
101
102<!-- MCP:END -->
103
104## Anti-Patterns
105
106- Claiming a Stitch screen-generation, screen-editing, or screen-retrieval MCP call succeeded when the active host does not expose that tool.
107- Uploading files, screenshots, HTML, markdown, or design assets to Stitch without user-approved destination and artifact details.
108- Reading, printing, storing, or committing Stitch API keys, MCP config secrets, cookies, or credential-bearing files.
109- Treating generated design or code as final without local render, syntax, or artifact verification.
110- Collapsing this workflow into a broader frontend/design skill when Stitch-specific files, project IDs, or design-system assets matter.
111
112## Verification Protocol
113
114Before claiming this skill was applied successfully:
115
1161. Pass/fail: `.stitch/DESIGN.md` exists and summarizes real source tokens.
1172. Pass/fail: The static HTML opens locally enough to inspect core layout and images.
1183. Pass/fail: Stitch design-system creation was MCP-verified or the fallback evidence is recorded.
1194. Pass/fail: No API key, token, cookie, or credential-bearing config was copied into durable files.
1205. Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable.
1216. Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior.
122
123## Related Skills
124
125- [stitch-extract-static-html](../stitch-extract-static-html/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
126- [stitch-extract-design-md](../stitch-extract-design-md/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
127- [stitch-manage-design-system](../stitch-manage-design-system/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
128- [stitch-upload-to-stitch](../stitch-upload-to-stitch/SKILL.md): Use when the task also needs this adjacent Stitch workflow.