stitch-loop

Coordinate Stitch MCP tooling to generate and integrate pages from baton prompts.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/eliuhads/stitch2elementor --skill stitch-loop-eliuhads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/eliuhads/stitch2elementor/tree/main/.agent/skills/stitch-loop
Command: npx skills add https://github.com/eliuhads/stitch2elementor --skill stitch-loop-eliuhads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates iterative, baton-driven website development by coordinating Stitch MCP tooling to produce pages and push them into the site in a continuous loop.

Core Features & Use Cases

  • Autonomous baton-loop that reads a baton file, generates a page with Stitch MCP tools, integrates it into the site structure, and writes the next task for the subsequent iteration.
  • Design-system driven prompts that rely on .stitch/DESIGN.md and .stitch/SITE.md to maintain visual consistency, enabling CI/CD and agent-chain workflows.
  • Scalable automation capable of chaining across agents (e.g., Jules) and production pipelines, minimizing manual intervention.

Quick Start

Instruct the Stitch Build Loop to begin by initializing or continuing the baton-driven sequence using your existing Stitch project context.

Frequently Asked Questions about stitch-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate iterative site-building from design files?

To automate iterative site-building, you coordinate Stitch MCP tooling to assemble pages from designs. This process reads baton prompts, generates pages, integrates them into the site structure, and writes the next task for continuous iteration.

Can I use a design system to maintain visual consistency across automated page generation?

Yes, design systems maintain visual consistency during automated page generation. The baton-loop relies on `.stitch/DESIGN.md` and `.stitch/SITE.md` files to drive design-system consistent prompts for each generated page.

How does baton-driven automation work for continuous website development?

Baton-driven automation reads a baton file, generates a page with Stitch MCP tools, integrates it into the site, and persists the next task state. This creates a continuous looping mechanism for repeated page generation and pipeline extension.

Can I chain autonomous site-building agents across a CI/CD pipeline?

Yes, autonomous site-building agents can chain across CI/CD pipelines. The baton-loop persists state for continuous looping, enabling scalable automation capable of chaining across agents and production pipelines with minimal manual intervention.

Do I need Stitch MCP tools to run the autonomous build loop?

Yes, Stitch MCP tools are required to run the autonomous build loop. The loop coordinates Stitch MCP tooling specifically to manage project creation, coordinate page generation, manage assets, and integrate pages into the site.