stitch-loop

Automated iterative website generation with Stitch MCP tools is driven by a baton-passing loop that reads next-prompt.md, generates a page, and writes the next baton for continuous progression. It removes manual handoffs during page creation.

Baton-passing for sequential site construction works by reading a prompt from next-prompt.md, generating a page with Stitch, then writing the next prompt back into next-prompt.md to drive deterministic loop continuation across iterations.

Yes, DESIGN.md and SITE.md files are required for design-system integration. They provide the context needed to maintain consistent visual structure and styling across all generated pages during the autonomous iteration loop.

Autonomous page generation loops support CI/CD triggers, agent chains, and human-in-the-loop oversight. The workflow orchestration writes the next baton to next-prompt.md, enabling seamless integration with automated deployment pipelines.

To maintain consistent visuals across automated page iterations, use SITE.md and DESIGN.md context files alongside Stitch MCP tools. The loop reads these files during each generation cycle to enforce design-system rules.