Extract Static HTML
Extract a self-contained static HTML file from any web application.
Which Strategy to Use
You MUST ask the user to choose which strategy to use before proceeding. Present the options clearly, recommend Strategy A as the preferred default, and provide a brief pros/cons summary for each option to help them make an informed decision.
|
Strategy A (Puppeteer) |
Strategy B (Browser Subagent) |
| When |
App runs locally, no auth wall |
Need to interact with page first (click, fill forms) |
| Fidelity |
Highest — computed styles resolved |
High — rendered DOM |
| Setup |
Zero — no mock needed |
Zero — no mock needed |
| Framework |
Any |
Any |
| Output |
Writes to file — no size limit |
May truncate in agent context |
[!WARNING]
Checkpoint — User Confirmation Required.
You MUST ask the user which strategy they prefer before proceeding.
Present the comparison table above, recommend Strategy A as the default, and
wait for explicit approval. Do NOT make the decision yourself or proceed
until the user confirms.
Strategy A: Puppeteer Snapshot (Recommended)
Launches headless Chrome, captures the fully rendered DOM, and produces a self-contained HTML file with all CSS inlined and images as base64. Works with any framework — no MockPage.jsx needed.
Prerequisites
- App running locally (e.g.,
npm run dev)
- Node.js with
puppeteer available (check: node -e "require('puppeteer')")
Workflow
Start the App and note the port.
[!WARNING]
Checkpoint — User Confirmation Required.
After starting the local server, you MUST pause and ask the user for
confirmation before running the snapshot script or launching a browser
subagent. Report the URL and port to the user so they can verify the app
is running and rendering correctly. Do NOT proceed to the snapshot
step until the user confirms.
Run the Snapshot Script:
npx tsx <SKILL_DIR>/scripts/snapshot.ts \
--url http://localhost:5173 \
--output .stitch/home.html \
--wait 2000
Multiple pages — run once per route:
npx tsx <SKILL_DIR>/scripts/snapshot.ts \
--url http://localhost:5173 --output .stitch/home.html --wait 2000
npx tsx <SKILL_DIR>/scripts/snapshot.ts \
--url http://localhost:5173/pricing --output .stitch/pricing.html --wait 2000
npx tsx <SKILL_DIR>/scripts/snapshot.ts \
--url http://localhost:5173/dashboard --output .stitch/dashboard.html --wait 2000 --html-class dark
Clean Up Dev Server:
If a local dev server was started specifically for snapshot extraction, make sure to stop the server process or terminate the background task once extraction is completed.
Script Flags
| Flag |
Default |
Description |
--url |
(required) |
URL to capture |
--output |
(required) |
Output file path |
--wait |
1000 |
Extra wait (ms) after network idle. Increase for lazy-loading apps. |
--viewport |
1280x800 |
Viewport size as WIDTHxHEIGHT |
--html-class |
— |
Class(es) for <html> element (e.g., dark) |
--remove-fixed |
false |
Remove fixed/sticky elements (cookie banners, chat widgets) |
--full-height |
false |
Resize viewport to full scroll height |
--title |
— |
Override page title (set to the route path, e.g. /dashboard or /settings/profile) |
--auth-script |
— |
Path to a JS/TS module that exports a default async (page) => void function for authentication |
--inline-canvas |
false |
Convert <canvas> elements (ECharts, Chart.js, D3) to base64 <img> tags |
What It Does Automatically
- Captures all CSSOM rules from
document.styleSheets (preserves dynamic Vite/Tailwind dev styles and CSS-in-JS)
- Inlines all
<link rel="stylesheet"> → <style> blocks
- Converts
<img> src and srcset → base64 data URIs (skips external fonts)
- Inlines same-origin and relative icon font files (
@font-face) as base64 data URIs so ligatures never render as ASCII text
- Inlines
<source srcset> URLs as base64
- Removes failed/dead
srcset entries so the browser falls back to the inlined src
- Removes
<script> tags, Vite HMR dev style blocks (createHotContext, import.meta.hot), and dev overlays
- Resolves relative CSS
url() paths before inlining
Framework Notes
| Framework |
Notes |
| React + Vite |
Works out of the box. --wait 1000. |
| Next.js |
--wait 3000 for SSR hydration. URL: http://localhost:3000. <img srcset> from /_next/image is auto-inlined as base64. |
| Angular (@angular/cli / v17+) |
Works out of the box with ng serve (default URL: http://localhost:4200). --wait 2000 for Angular Material / PrimeNG animation hydration and lazy-loaded routes. |
| Vue / Nuxt |
Works out of the box. |
| Svelte / SvelteKit |
Works out of the box. |
| Storybook |
Use story URL: --url http://localhost:6006/?path=/story/... |
| SSR (Webpack) |
May need longer --wait. |
Troubleshooting
| Issue |
Solution |
| Images missing |
Increase --wait |
| Images show as broken after server stops |
Verify srcset was inlined — check log for "Inlined N images". If srcset URLs failed, they are auto-removed so src (inlined) is used. |
| Icons display as text / Serif unstyled font |
Ensure snapshot.ts captures CSSOM from document.styleSheets (step 0) and same-origin icon fonts (@font-face) are inlined as base64 data URIs. |
Next.js /_next/image not inlined |
Ensure the dev server is running when snapshot runs — the script fetches optimized images from the running server. |
| Dark mode not applied |
--html-class dark |
| Cookie banner in output |
--remove-fixed |
| Page requires login |
Use --auth-script ./auth.ts (see Auth-Gated Pages below) |
| Charts/graphs show as blank boxes |
Use --inline-canvas to serialize <canvas> to base64 <img> |
Cannot find module 'puppeteer' |
npm install -g puppeteer |
Auth-Gated Pages
For apps with login guards (Vue Router beforeEach, React ProtectedRoute, etc.), create a small auth script that runs in the Puppeteer session:
// auth-myapp.ts
import type { Page } from 'puppeteer';
export default async function authenticate(page: Page) {
// Example 1: Fill and submit a login form
await page.type('#username', 'admin');
await page.type('#password', 'password123');
await page.click('#login-button');
await page.waitForNavigation({ waitUntil: 'networkidle2' });
// Example 2: Inject cookies/localStorage directly
// await page.evaluate(() => {
// localStorage.setItem('token', 'mock-jwt-token');
// });
// Example 3: Call the app's own login API via module injection (Vue/Vite)
// await page.evaluate(() => {
// return new Promise((resolve) => {
// const script = document.createElement('script');
// script.type = 'module';
// script.textContent = `
// import { useUserStore } from '/src/store/modules/user.ts';
// import { fetchLogin } from '/src/api/auth.ts';
// const res = await fetchLogin({ userName: 'Admin', password: '123456' });
// useUserStore().setToken(res.token, res.refreshToken);
// window.dispatchEvent(new CustomEvent('auth-done'));
// `;
// document.head.appendChild(script);
// window.addEventListener('auth-done', () => resolve(true), { once: true });
// });
// });
}
Then use it:
npx tsx <SKILL_DIR>/scripts/snapshot.ts \
--url http://localhost:5173/#/dashboard \
--output .stitch/dashboard.html \
--auth-script ./auth-myapp.ts \
--inline-canvas \
--wait 5000
The script navigates to the --url first (which may redirect to login), runs your auth function, then re-navigates to the original --url with the authenticated session.
Strategy B: Browser Subagent Capture
Use when you need to interact with the page (click buttons, fill forms, navigate tabs) before capturing. The browser subagent gives you full control but output may truncate for large pages.
Workflow
Start the App locally.
Navigate using a browser subagent.
Interact as needed (click, scroll, fill forms).
Extract DOM: document.documentElement.outerHTML
[!WARNING]
Large pages may truncate. To handle this:
- Remove
<style> tags before extraction: document.querySelectorAll('style').forEach(el => el.remove())
- Re-add styles statically (Tailwind CDN link, source CSS)
Save to file.
Appendix: Static Fallback (MockPage.jsx)
[!NOTE]
This method is a last resort for when the app cannot run locally (broken deps, missing backend, auth walls with no bypass). It requires manually flattening React components into a single JSX file. Prefer Strategy A whenever possible.
When to Use
- App can't run locally at all
- Page requires auth with no mock/bypass
- You need a specific UI state that's impossible to reach by navigation (error screens, empty states)
Quick Reference
npx tsx <SKILL_DIR>/scripts/extract_inline_html.ts \
--index-css src/css/App.css \
--extra-css index.html \
--outdir .stitch \
--page src/MockPage.jsx:Page.html:"Page Title"
Key flags: --no-tailwind (non-Tailwind apps), --html-class dark (dark mode), --css-files (extra CSS files).
Auto-detection: Tailwind config is auto-detected. @apply directives automatically use <style type="text/tailwindcss">.
MockPage.jsx Rules
- Include the full layout — header, sidebar, footer (read
App.js first)
- Flatten all conditionals — pick one state, remove all ternaries and
&& guards
- Hardcode all data — replace
{variable} with concrete values, unroll .map() loops
- Preserve logos — use
<img> with local paths (post-process will inline them)
- Remove floating elements — cookie banners, chat widgets, feedback buttons
Post-Processing
Inline local images:
npx tsx <SKILL_DIR>/scripts/post_process.ts \
.stitch/Page.html --base-dir <app-directory>
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-extract-static-html and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Stitch MCP
- Fallback prompt: "Use the Extract Static HTML 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: The output HTML exists under
.stitch/.
- Pass/fail: Capture route, viewport, wait time, and special flags are recorded.
- Pass/fail: Important images are inlined or intentionally left as stable external URLs.
- Pass/fail: No authenticated personal content, cookies, tokens, or private user data were captured.
- 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-extract-static-html
3version: "2.0"
4last_updated: 2026-09-08
5tags: [stitch, html, frontend, snapshot, assets]
6description: "Capture a self-contained static HTML snapshot from a running app or mock component so it can be reviewed or uploaded to Stitch."
7license: "Apache-2.0"
8metadata:
9 source: https://skillmd.com/skills/practicalswan/stitch-extract-static-html
10---
11
12# Extract Static HTML
13
14Extract a self-contained static HTML file from any web application.
15
16## Which Strategy to Use
17
18You MUST ask the user to choose which strategy to use before proceeding. Present the options clearly, **recommend Strategy A** as the preferred default, and **provide a brief pros/cons summary** for each option to help them make an informed decision.
19
20| | Strategy A (Puppeteer) | Strategy B (Browser Subagent) |
21| :--- | :--- | :--- |
22| **When** | App runs locally, no auth wall | Need to interact with page first (click, fill forms) |
23| **Fidelity** | **Highest — computed styles resolved** | High — rendered DOM |
24| **Setup** | **Zero — no mock needed** | Zero — no mock needed |
25| **Framework** | **Any** | Any |
26| **Output** | **Writes to file — no size limit** | May truncate in agent context |
27
28> [!WARNING]
29> **Checkpoint — User Confirmation Required.**
30> You **MUST** ask the user which strategy they prefer before proceeding.
31> Present the comparison table above, recommend Strategy A as the default, and
32> wait for explicit approval. Do **NOT** make the decision yourself or proceed
33> until the user confirms.
34
35***
36
37## Strategy A: Puppeteer Snapshot (Recommended)
38
39Launches headless Chrome, captures the fully rendered DOM, and produces a self-contained HTML file with all CSS inlined and images as base64. Works with **any framework** — no MockPage.jsx needed.
40
41### Prerequisites
42
43- App running locally (e.g., `npm run dev`)
44- Node.js with `puppeteer` available (check: `node -e "require('puppeteer')"`)
45
46### Workflow
47
481. **Start the App** and note the port.
49
50 > [!WARNING]
51 > **Checkpoint — User Confirmation Required.**
52 > After starting the local server, you **MUST** pause and ask the user for
53 > confirmation before running the snapshot script or launching a browser
54 > subagent. Report the URL and port to the user so they can verify the app
55 > is running and rendering correctly. Do **NOT** proceed to the snapshot
56 > step until the user confirms.
57
582. **Run the Snapshot Script**:
59 ```bash
60 npx tsx <SKILL_DIR>/scripts/snapshot.ts \
61 --url http://localhost:5173 \
62 --output .stitch/home.html \
63 --wait 2000
64 ```
65
663. **Multiple pages** — run once per route:
67 ```bash
68 npx tsx <SKILL_DIR>/scripts/snapshot.ts \
69 --url http://localhost:5173 --output .stitch/home.html --wait 2000
70 npx tsx <SKILL_DIR>/scripts/snapshot.ts \
71 --url http://localhost:5173/pricing --output .stitch/pricing.html --wait 2000
72 npx tsx <SKILL_DIR>/scripts/snapshot.ts \
73 --url http://localhost:5173/dashboard --output .stitch/dashboard.html --wait 2000 --html-class dark
74 ```
75
764. **Clean Up Dev Server**:
77 If a local dev server was started specifically for snapshot extraction, make sure to stop the server process or terminate the background task once extraction is completed.
78
79
80### Script Flags
81
82| Flag | Default | Description |
83| :--- | :--- | :--- |
84| `--url` | *(required)* | URL to capture |
85| `--output` | *(required)* | Output file path |
86| `--wait` | `1000` | Extra wait (ms) after network idle. Increase for lazy-loading apps. |
87| `--viewport` | `1280x800` | Viewport size as `WIDTHxHEIGHT` |
88| `--html-class` | — | Class(es) for `<html>` element (e.g., `dark`) |
89| `--remove-fixed` | `false` | Remove fixed/sticky elements (cookie banners, chat widgets) |
90| `--full-height` | `false` | Resize viewport to full scroll height |
91| `--title` | — | Override page title (set to the route path, e.g. `/dashboard` or `/settings/profile`) |
92| `--auth-script` | — | Path to a JS/TS module that exports a default `async (page) => void` function for authentication |
93| `--inline-canvas` | `false` | Convert `<canvas>` elements (ECharts, Chart.js, D3) to base64 `<img>` tags |
94
95### What It Does Automatically
96
97- Captures all CSSOM rules from `document.styleSheets` (preserves dynamic Vite/Tailwind dev styles and CSS-in-JS)
98- Inlines all `<link rel="stylesheet">` → `<style>` blocks
99- Converts `<img>` `src` **and `srcset`** → base64 data URIs (skips external fonts)
100- Inlines same-origin and relative icon font files (`@font-face`) as base64 data URIs so ligatures never render as ASCII text
101- Inlines `<source srcset>` URLs as base64
102- Removes failed/dead `srcset` entries so the browser falls back to the inlined `src`
103- Removes `<script>` tags, Vite HMR dev style blocks (`createHotContext`, `import.meta.hot`), and dev overlays
104- Resolves relative CSS `url()` paths before inlining
105
106### Framework Notes
107
108| Framework | Notes |
109| :--- | :--- |
110| **React + Vite** | Works out of the box. `--wait 1000`. |
111| **Next.js** | `--wait 3000` for SSR hydration. URL: `http://localhost:3000`. `<img srcset>` from `/_next/image` is auto-inlined as base64. |
112| **Angular (@angular/cli / v17+)** | Works out of the box with `ng serve` (default URL: `http://localhost:4200`). `--wait 2000` for Angular Material / PrimeNG animation hydration and lazy-loaded routes. |
113| **Vue / Nuxt** | Works out of the box. |
114| **Svelte / SvelteKit** | Works out of the box. |
115| **Storybook** | Use story URL: `--url http://localhost:6006/?path=/story/...` |
116| **SSR (Webpack)** | May need longer `--wait`. |
117
118### Troubleshooting
119
120| Issue | Solution |
121| :--- | :--- |
122| Images missing | Increase `--wait` |
123| Images show as broken after server stops | Verify `srcset` was inlined — check log for "Inlined N images". If `srcset` URLs failed, they are auto-removed so `src` (inlined) is used. |
124| Icons display as text / Serif unstyled font | Ensure `snapshot.ts` captures CSSOM from `document.styleSheets` (step 0) and same-origin icon fonts (`@font-face`) are inlined as base64 data URIs. |
125| Next.js `/_next/image` not inlined | Ensure the dev server is running when snapshot runs — the script fetches optimized images from the running server. |
126| Dark mode not applied | `--html-class dark` |
127| Cookie banner in output | `--remove-fixed` |
128| Page requires login | Use `--auth-script ./auth.ts` (see Auth-Gated Pages below) |
129| Charts/graphs show as blank boxes | Use `--inline-canvas` to serialize `<canvas>` to base64 `<img>` |
130| `Cannot find module 'puppeteer'` | `npm install -g puppeteer` |
131
132### Auth-Gated Pages
133
134For apps with login guards (Vue Router `beforeEach`, React `ProtectedRoute`, etc.), create a small auth script that runs in the Puppeteer session:
135
136```ts
137// auth-myapp.ts
138import type { Page } from 'puppeteer';
139
140export default async function authenticate(page: Page) {
141 // Example 1: Fill and submit a login form
142 await page.type('#username', 'admin');
143 await page.type('#password', 'password123');
144 await page.click('#login-button');
145 await page.waitForNavigation({ waitUntil: 'networkidle2' });
146
147 // Example 2: Inject cookies/localStorage directly
148 // await page.evaluate(() => {
149 // localStorage.setItem('token', 'mock-jwt-token');
150 // });
151
152 // Example 3: Call the app's own login API via module injection (Vue/Vite)
153 // await page.evaluate(() => {
154 // return new Promise((resolve) => {
155 // const script = document.createElement('script');
156 // script.type = 'module';
157 // script.textContent = `
158 // import { useUserStore } from '/src/store/modules/user.ts';
159 // import { fetchLogin } from '/src/api/auth.ts';
160 // const res = await fetchLogin({ userName: 'Admin', password: '123456' });
161 // useUserStore().setToken(res.token, res.refreshToken);
162 // window.dispatchEvent(new CustomEvent('auth-done'));
163 // `;
164 // document.head.appendChild(script);
165 // window.addEventListener('auth-done', () => resolve(true), { once: true });
166 // });
167 // });
168}
169```
170
171Then use it:
172```bash
173npx tsx <SKILL_DIR>/scripts/snapshot.ts \
174 --url http://localhost:5173/#/dashboard \
175 --output .stitch/dashboard.html \
176 --auth-script ./auth-myapp.ts \
177 --inline-canvas \
178 --wait 5000
179```
180
181The script navigates to the `--url` first (which may redirect to login), runs your auth function, then **re-navigates** to the original `--url` with the authenticated session.
182
183***
184
185## Strategy B: Browser Subagent Capture
186
187Use when you need to **interact with the page** (click buttons, fill forms, navigate tabs) before capturing. The browser subagent gives you full control but output may truncate for large pages.
188
189### Workflow
190
1911. **Start the App** locally.
1922. **Navigate** using a browser subagent.
1933. **Interact** as needed (click, scroll, fill forms).
1944. **Extract DOM**: `document.documentElement.outerHTML`
195
196 > [!WARNING]
197 > Large pages may truncate. To handle this:
198 > - Remove `<style>` tags before extraction: `document.querySelectorAll('style').forEach(el => el.remove())`
199 > - Re-add styles statically (Tailwind CDN link, source CSS)
2005. **Save** to file.
201
202***
203
204## Appendix: Static Fallback (MockPage.jsx)
205
206> [!NOTE]
207> This method is a **last resort** for when the app cannot run locally (broken deps, missing backend, auth walls with no bypass). It requires manually flattening React components into a single JSX file. **Prefer Strategy A whenever possible.**
208
209### When to Use
210
211- App can't run locally at all
212- Page requires auth with no mock/bypass
213- You need a specific UI state that's impossible to reach by navigation (error screens, empty states)
214
215### Quick Reference
216
217```bash
218npx tsx <SKILL_DIR>/scripts/extract_inline_html.ts \
219 --index-css src/css/App.css \
220 --extra-css index.html \
221 --outdir .stitch \
222 --page src/MockPage.jsx:Page.html:"Page Title"
223```
224
225**Key flags**: `--no-tailwind` (non-Tailwind apps), `--html-class dark` (dark mode), `--css-files` (extra CSS files).
226
227**Auto-detection**: Tailwind config is auto-detected. `@apply` directives automatically use `<style type="text/tailwindcss">`.
228
229### MockPage.jsx Rules
230
2311. **Include the full layout** — header, sidebar, footer (read `App.js` first)
2322. **Flatten all conditionals** — pick one state, remove all ternaries and `&&` guards
2333. **Hardcode all data** — replace `{variable}` with concrete values, unroll `.map()` loops
2344. **Preserve logos** — use `<img>` with local paths (post-process will inline them)
2355. **Remove floating elements** — cookie banners, chat widgets, feedback buttons
236
237### Post-Processing
238
239Inline local images:
240```bash
241npx tsx <SKILL_DIR>/scripts/post_process.ts \
242 .stitch/Page.html --base-dir <app-directory>
243```
244
245<!-- MCP:START -->
246
247<!-- PORTABILITY:START -->
248## Cross-Client Portability
249
250This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
251
252- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
253 workflow in project instructions when folder discovery is unavailable.
254- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
255- Codex: install or sync the folder into
256 `$CODEX_HOME/skills/stitch-extract-static-html` and restart Codex after major changes.
257
258<!-- PORTABILITY:END -->
259
260## MCP Availability And Fallback
261
262Preferred MCP Server: Stitch MCP
263
264- Fallback prompt: "Use the Extract Static HTML skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
265- 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.
266- Do not claim screen lookup, generation, editing, or variant MCP calls unless those tools are present in the active host tool list.
267- Do not claim an MCP operation was used when the active host does not expose it.
268
269<!-- MCP:END -->
270
271## Anti-Patterns
272
273- Claiming a Stitch screen-generation, screen-editing, or screen-retrieval MCP call succeeded when the active host does not expose that tool.
274- Uploading files, screenshots, HTML, markdown, or design assets to Stitch without user-approved destination and artifact details.
275- Reading, printing, storing, or committing Stitch API keys, MCP config secrets, cookies, or credential-bearing files.
276- Treating generated design or code as final without local render, syntax, or artifact verification.
277- Collapsing this workflow into a broader frontend/design skill when Stitch-specific files, project IDs, or design-system assets matter.
278
279## Verification Protocol
280
281Before claiming this skill was applied successfully:
282
2831. Pass/fail: The output HTML exists under `.stitch/`.
2842. Pass/fail: Capture route, viewport, wait time, and special flags are recorded.
2853. Pass/fail: Important images are inlined or intentionally left as stable external URLs.
2864. Pass/fail: No authenticated personal content, cookies, tokens, or private user data were captured.
2875. Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable.
2886. Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior.
289
290## Related Skills
291
292- [stitch-code-to-design](../stitch-code-to-design/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
293- [stitch-upload-to-stitch](../stitch-upload-to-stitch/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
294- [web-testing](../web-testing/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
295- [vite-development](../vite-development/SKILL.md): Use when the task also needs this adjacent Stitch workflow.