stitch-loop

Automating iterative Stitch site builds requires an autonomous loop that reads baton prompts from next-prompt.md, generates pages with Stitch MCP, and advances the baton. This coordinates continuous site construction, integration, and publishing without manual intervention.

In autonomous website generation, a baton prompt is a file named next-prompt.md that stores the current task instructions. The loop reads this baton, generates the requested page, and writes the next baton to continue the iteration cycle.

Yes, SITE.md and DESIGN.md files are required to use Stitch MCP for page generation. These files provide the project context required to maintain project vision and design consistency across all autonomous iterations.

You can persist your Stitch project ID across multiple site iterations by saving it within a stitch.json file. This ensures the autonomous loop maintains the correct project context during continuous page generation.

To maintain design consistency across autonomous page generation cycles, leverage context-aware prompting with SITE.md and DESIGN.md files. This ensures every generated page aligns with the established project vision.

Yes, agent chains can be used for continuous website generation and publishing by orchestrating a Stitch-driven loop. It reads baton prompts, integrates newly generated pages into the site structure, and prepares the next baton automatically.