In the Skill's Own Terms
Converts an existing frontend codebase (React + Vite, Next.js, Angular, Vue) into a Stitch Design by chaining three skills: extract-static-html, extract-design-md and upload-to-stitch. It targets designers and developers moving a running app or a built web directory into Stitch so they can iterate on it there.
The workflow extracts one self-contained HTML file, writes a design system to .stitch/DESIGN.md, creates the design system in Stitch, then uploads the HTML as a screen titled with the page's route path. It is the required path for save, migrate or upload requests, and HTML verification is optional and never blocks the run.
What it produces
- One self-contained HTML file, for example /path/to/extracted/standalone.html.
- A design system description written as DESIGN.md.
- A screen uploaded to Stitch whose name and title identify the route it came from in the application.
How It Works
- 01Extract a self-contained HTML File
Hands off to the extract-static-html skill, which works from the build output or a running dev server such as Vite or Angular CLI ng serve and produces one standalone HTML file.
- 02Offer Verification Without Pausing
After extraction you tell the user where the file is so they can check it themselves in a browser, and the run continues to the next step regardless.
- 03Analyze the Source into a Design System
The extract-design-md skill reads the project's components, stylesheets and theme configs, and its result is written out as a design system file.
- 04Create the Design System in Stitch
The manage-design-system skill uploads DESIGN.md and calls create_design_system_from_design_md with the required schemas.
- 05Upload the HTML as a Screen
The same upload script sends the standalone HTML using the Stitch API key and projectId, with the title argument set to the page route so the screen is identifiable in Stitch.