This skill teaches an agent to run the Stitch Build Loop. Each iteration reads the task from .stitch/next-prompt.md, generates a screen with the Stitch MCP tools, saves it into the site folder, updates the sitemap and writes the next task back to the baton file.
It relies on DESIGN.md and SITE.md for style and scope, and can check the page visually through the Chrome DevTools MCP server.
What You Get
- Generated pages saved under site/public
- Design downloads in .stitch/designs with HTML and screenshots
- A .stitch/metadata.json holding project and screen IDs
- An updated SITE.md sitemap and a fresh next-prompt.md after each pass
Common Use Cases
- Building a five-page portfolio site from a single starting prompt
- Running page generation from CI whenever the baton file changes
- Keeping a multi-page site consistent through one design system
What Makes It Unique
The baton file turns page generation into a relay that any orchestration layer can drive, from a human to a CI job to chained agents. Every prompt carries the design system block, so pages share one visual language.
Under The Hood
The agent calls Stitch MCP tools to create projects and generate screens, downloads HTML and screenshots, and moves files into site/public. It uses the shell to start and stop a local dev server such as npx serve when the optional Chrome DevTools MCP check is available, and it writes the baton, sitemap and metadata files.