stitch-loop

Automated iterative web page generation uses a baton-passing loop that reads instructions from next-prompt.md, generates pages via Stitch MCP tools, and queues the next task. This autonomous cycle coordinates Stitch server access with DESIGN.md and SITE.md context to continuously build and integrate site pages.

An autonomous baton-passing loop is an iteration pattern for website development where an agent reads a baton from next-prompt.md, generates a page using Stitch MCP tools, and writes the next instruction. It enables continuous, hands-off site building by coordinating context across DESIGN.md and SITE.md files.

Continuous website generation with Stitch MCP tools requires a next-prompt.md baton file, a DESIGN.md for styling context, and a SITE.md for structure. Triggering the loop reads the baton, generates a page, updates site navigation, and writes the next iteration task to maintain the autonomous cycle.

Autonomous page generation integrates into CI/CD workflows and agent chains by reading the next-prompt.md baton, generating pages with Stitch MCP tools, and queuing subsequent instructions. This loop pattern automates deployment pipelines for iterative site-building tasks without manual intervention.

A Stitch server is required to run an autonomous baton-powered web loop. The loop coordinates access to the Stitch server alongside DESIGN.md and SITE.md files, using MCP tools to generate pages and update site structure while passing the baton to the next iteration.

Avoid using a baton-passing loop for frontend automation when site-building tasks are non-iterative or require manual design decisions. The autonomous loop pattern is designed for continuous, repetitive page generation and integration within a Stitch project, not for isolated or highly customized one-off page creations.