stitch-loop

Orchestrate baton-driven Stitch page generation and integration from .stitch/next-prompt.md.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/moonseokchoi-kr/moon-harness --skill stitch-loop-moonseokchoi-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/moonseokchoi-kr/moon-harness/tree/main/skills/stitch-loop
Command: npx skills add https://github.com/moonseokchoi-kr/moon-harness --skill stitch-loop-moonseokchoi-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Stitch loop enables autonomous, baton-driven iteration for building and integrating website pages, reducing manual toil and speeding delivery.

Core Features & Use Cases

  • Baton-based iteration: read .stitch/next-prompt.md, generate pages with Stitch MCP tools, and integrate them into the site.
  • Prerequisites and orchestration: requires a Stitch project, DESIGN.md and SITE.md, and a defined roadmap for continuous development.
  • Use Case: teams iteratively add pages, adjust design, and validate layouts through automated prompts.

Quick Start

Initialize a Stitch project, ensure the baton file exists at .stitch/next-prompt.md, and start the loop to begin the first iteration.

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 generation for new Stitch pages?

You can automate iterative Stitch page generation by orchestrating baton-driven loops that read .stitch/next-prompt.md, generate pages via the Stitch MCP, and integrate them continuously. This reduces manual toil and speeds up iterative website delivery.

What files do I need to set up before starting automated Stitch page integration?

To set up automated Stitch page integration, you need a .stitch/SITE.md file for site structure, a .stitch/DESIGN.md for design-system compliance, and a baton workflow file at .stitch/next-prompt.md. A Stitch MCP server and .stitch/metadata.json for projectId tracking are also required.

How does baton-based iteration work for continuous website development?

Baton-based iteration works by reading the next prompt from .stitch/next-prompt.md, generating the requested page with Stitch MCP tools, and integrating it into the existing site. This sequence continuously builds and integrates pages while maintaining design consistency.

Can I verify generated Stitch pages automatically during the build loop?

Yes, you can verify generated Stitch pages automatically during the build loop. The orchestration supports optional Chrome DevTools integration, allowing you to validate layouts and design-system compliance through automated prompts within the iteration cycle.

Does automated Stitch site generation require a specific project configuration?

Automated Stitch site generation requires a configured Stitch project with defined DESIGN.md and SITE.md files. It also requires projectId tracking in .stitch/metadata.json and a defined roadmap for continuous development to handle tasks like updating site structure.