stitch::extract-static-html

A self-contained HTML snapshot inlines all CSS and images into a single portable file. This Skill uses deterministic Puppeteer scripts or interactive browser subagents to capture running UI states and embed assets locally.

Yes, the asset inlining workflow supports React, Vue, Svelte, and vanilla HTML applications. It captures the rendered DOM state across these frameworks and processes the output using AST parsing utilities to embed external resources.

The best way to capture a specific UI state for portable sharing is using deterministic Puppeteer-based snapshots. This approach renders the exact application state and embeds all assets locally into a self-contained file ready for upload.

Yes, you can use interactive browser subagent flows as an alternative to deterministic Puppeteer snapshots for HTML extraction. Both workflows capture the UI and enforce asset inlining to produce a portable self-contained page.

The HTML snapshot process requires Babel dependencies including @babel/parser, @babel/traverse, and @babel/generator to parse, traverse, and generate code during post-processing. These utilities allow deterministic DOM manipulation for asset inlining.

You should not use Puppeteer for web-automation asset inlining when you need to capture interactive user journeys rather than a static DOM state. In such cases, interactive browser subagent flows provide a more suitable alternative for HTML extraction.