stitch-loop

Automates iterative website generation using Stitch MCP tools through a baton-passing loop pattern.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/khulnasoft-bot/scalify --skill stitch-loop-khulnasoft-bot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/khulnasoft-bot/scalify/tree/main/skills/plugins/stitch-utilities/skills/stitch-loop
Command: npx skills add https://github.com/khulnasoft-bot/scalify --skill stitch-loop-khulnasoft-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a multi-page website with AI-generated designs requires repetitive manual prompting, file management, and navigation wiring for each page. This Skill turns that into an autonomous loop where each iteration reads a task, generates a page with Stitch, integrates it into the site, and queues the next task. ## Core Features & Use Cases - Baton-Passing Loop: Reads the current task from .stitch/next-prompt.md, generates the page via Stitch MCP tools, then writes the next task to keep the loop alive. - Site Context Management: Maintains .stitch/SITE.md (vision, sitemap, roadmap) and .stitch/DESIGN.md (design system) so every generated page stays consistent and no page is recreated. - Project State Persistence: Stores Stitch project and screen IDs in .stitch/metadata.json for future edits, plus optional visual verification via Chrome DevTools MCP. - Use Case: A developer sets up a furniture showroom site, seeds the roadmap in SITE.md, and lets the agent autonomously build the contact page, product pages, and gallery one iteration at a time, triggered manually or via CI/CD. ## Quick Start Read my .stitch/next-prompt.md file, generate the page using Stitch, integrate it into the site, and prepare the next iteration.

Frequently Asked Questions about stitch-loop

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

FAQPage Schema
How do I set up an autonomous website build loop with Stitch?▼

Create a .stitch directory containing DESIGN.md, SITE.md, and a next-prompt.md baton file with a page field in its YAML frontmatter. The agent reads the baton, generates the page via Stitch MCP tools, integrates it into site/public, and writes the next baton.

What is the next-prompt.md baton file format?▼

The baton is a Markdown file with YAML frontmatter containing a page field (the output filename without extension) and a body with the full Stitch prompt. The body must include the design system block copied from DESIGN.md and a numbered page structure.

Does the stitch-loop skill work with CI/CD pipelines?▼

Yes, the loop is orchestration-agnostic. GitHub Actions can trigger new iterations on changes to next-prompt.md, and it also supports human-in-the-loop review, agent chains like the Jules API, or manual repeated runs.

Why does the build loop stall or stop continuing?▼

The loop stalls when the agent forgets to update .stitch/next-prompt.md before completing, or writes it with invalid frontmatter. Always verify the baton has a valid page field and includes the design system block.

Can I verify generated pages visually before publishing?▼

Yes, if the Chrome DevTools MCP Server is available, the skill starts a local dev server, navigates to the generated page, captures a screenshot, and compares it against the Stitch screenshot for fidelity. This step is optional.