stitch-loop

Automating iterative frontend site builds requires orchestrating Stitch-driven generation cycles and integrating each page into the site structure. This is achieved by using a baton file to pass task context between iterations.

A baton-driven workflow uses a next-prompt.md file to pass task instructions to the next iteration. The orchestrator reads this baton file, generates a Stitch page, integrates it, and writes the next task back for the following cycle.

Yes, using Stitch MCP tools for site generation requires a defined Design System prompt block. You also need a SITE.md file to define the roadmap and a running Stitch server before starting the automation loop.

To start an autonomous iteration loop, initialize the next-prompt.md baton file with a starting page description. Then, launch the orchestrator to handle Stitch generation, site integration, and subsequent baton updates automatically.

Using a baton file for iterative site integration depends heavily on maintaining strict environment readiness. The loop requires continuous access to a Stitch server and accurate updates to next-prompt.md to avoid breaking task handoffs across iterations.