stitch-loop

Automating iterative website generation with Stitch requires reading a baton prompt and using Stitch MCP tools to create projects, generate screens, fetch assets, and update site navigation autonomously. This loop continuously builds pages while advancing the baton for the next iteration.

A baton-driven workflow for frontend development uses a prompt file, typically .stitch/next-prompt.md, to pass tasks sequentially. The system reads the baton, generates a page, integrates it, and writes the next task back to the file to keep the loop moving continuously.

To set up context for autonomous Stitch site builds, provide .stitch/SITE.md and .stitch/DESIGN.md files in your project. These documents guide page creation and prioritization by supplying the necessary site design and roadmap context for the generation workflow.

The Stitch MCP tool integrates new pages by fetching generated assets and applying site integration rules to update site navigation. This ensures newly generated screens are properly connected to the ongoing project structure during the baton loop.

Yes, you can use workflow orchestration to continuously improve a Stitch website by running a baton loop. After generating and integrating each page, the workflow writes the next task back to the baton file, enabling autonomous, continuous iteration for multi-step development.

To start a new Stitch iteration loop, provide a new baton prompt with a target page name and a Design System block. This initiates the next iteration, allowing the workflow to autonomously generate, validate, and integrate the new page into the site.