--- name: stitch-extract-static-html version: "1.2" last_updated: 2026-06-15 tags: [stitch, html, frontend, snapshot, assets] description: "Capture a self-contained static HTML snapshot from a running app or mock component so it can be reviewed or uploaded to Stitch." license: Apache-2.0 --- # Stitch Extract Static HTML This skill is a catalog-normalized import from `https://github.com/google-labs-code/stitch-skills` at commit `1544aa4a3be93e7515b0c27d32722f7ca5a2f691`, source path `plugins/stitch-design/skills/extract-static-html`. The upstream control file was corrected for this workspace: the verified Stitch MCP surface here is design-system oriented, so screen lookup, screen generation, and screen editing tools must be used only when the current host explicitly exposes them. ## When to Use This Skill - Use when a route or UI state must become standalone HTML for review or Stitch upload. - The task involves Google Stitch project IDs, `.stitch/` artifacts, DESIGN.md files, Stitch exports, or Stitch-specific validation. - The broader `stitch-design` router points here as the narrowest workflow. ## Workflow 1. Prefer `scripts/snapshot.ts` when the app can run locally without auth blockers. 2. Use interactive browser capture only when clicks, form input, or navigation are needed first. 3. Use static mock fallback only when the app cannot run and the user accepts a manually flattened state. 4. Start or identify the dev server and record the URL before capture. 5. Run `npx tsx scripts/snapshot.ts --url --output .stitch/.html` with matched viewport and wait flags. 6. Open or parse the output to confirm CSS, images, and critical layout survived script removal. ## Local Assets - `examples/`, `resources/`, `references/`, or `reference/` are upstream support material when present. Treat `SKILL.md` as the source of truth if a support file mentions an unavailable MCP tool. - `scripts/` are optional helpers. On Windows, prefer PowerShell or Node equivalents unless Git Bash or WSL is actually available. - Keep generated `.stitch/` files out of commits unless the user explicitly wants them as durable examples. ## Corrected Stitch MCP Surface Verified in this workspace on 2026-06-15: `create_project`, `upload_design_md`, `create_design_system_from_design_md`, `list_design_systems`, and `apply_design_system`. Do not claim `list_projects`, `list_screens`, `get_project`, `get_screen`, `generate_screen_from_text`, `edit_screens`, or `generate_variants` were used unless the current host exposes those exact tools in the active tool list. ## 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: 1. Pass/fail: The output HTML exists under `.stitch/`. 2. Pass/fail: Capture route, viewport, wait time, and special flags are recorded. 3. Pass/fail: Important images are inlined or intentionally left as stable external URLs. 4. Pass/fail: No authenticated personal content, cookies, tokens, or private user data were captured. 5. Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable. 6. Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior. ## Cross-Client Portability This skill is written to stay usable across GitHub Copilot, Claude Code, Codex, and Gemini CLI. - GitHub Copilot: keep the folder in a Copilot-visible skill or plugin path, or wrap the workflow as project instructions if the host does not support portable skill folders directly. - Claude Code: keep the folder in a local skills directory or a compatible plugin or marketplace source. - Codex: install or sync the folder into `$CODEX_HOME/skills/` and restart Codex after major changes. - Gemini CLI: this repository generates a project command named `/skills:stitch-extract-static-html` from this skill. Rebuild commands with `python scripts/export-gemini-skill.py stitch-extract-static-html` and then run `/commands reload` inside Gemini CLI. ## MCP Availability And Fallback Preferred MCP Server: Stitch MCP - Fallback prompt: "Use the Stitch Extract Static HTML skill without Stitch MCP. Use browser export or a manually flattened mock component when Puppeteer is unavailable, then document fidelity limits. Show the exact files, commands, manual Stitch UI steps, and verification evidence used before concluding." - Verified Stitch MCP tools in this workspace are design-system/project oriented; use broader screen tools only when the current host exposes them. - Use local scripts, exported HTML/screenshots, the Stitch web UI, and project metadata files as the fallback evidence path. ## Related Skills - [stitch-code-to-design](../stitch-code-to-design/SKILL.md): Use when the task also needs this adjacent Stitch workflow. - [stitch-upload-to-stitch](../stitch-upload-to-stitch/SKILL.md): Use when the task also needs this adjacent Stitch workflow. - [web-testing](../web-testing/SKILL.md): Use when the task also needs this adjacent Stitch workflow. - [vite-development](../vite-development/SKILL.md): Use when the task also needs this adjacent Stitch workflow.