stitch-loop

Generate website pages via Stitch MCP and integrate them into site/public.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/involvex/happy-vibecode --skill stitch-loop-involvex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/involvex/happy-vibecode/tree/main/.agents/skills/stitch-loop
Command: npx skills add https://github.com/involvex/happy-vibecode --skill stitch-loop-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The stitch-loop Skill removes the manual, error-prone work of repeatedly generating, integrating, and sequencing website pages by establishing an autonomous baton-passing workflow that reads a task, generates a screen with Stitch, integrates assets into the site, updates project metadata, and writes the next task.

Core Features & Use Cases

  • Baton-driven Iterations: Uses a single baton file to coordinate successive agent iterations and ensure continuous progress.
  • Stitch MCP Integration: Calls Stitch MCP create/get/generate APIs to create projects, generate screens, and persist screen metadata.
  • Asset Retrieval & Integration: Downloads HTML and screenshots, moves HTML into site/public, fixes asset paths, and updates navigation and site documentation.
  • Project State Management: Persists a .stitch/metadata.json map of project and screen identifiers and enforces sitemap and roadmap checks.
  • Optional Visual Verification: Supports Chrome DevTools MCP for automated rendering and screenshot comparisons when available.
  • Use cases include autonomous site expansion in CI/CD pipelines, iterative agent-driven prototyping, and low-touch content generation for marketing or product sites.

Quick Start

Use the stitch-loop skill to read the baton from .stitch/next-prompt.md, generate the page via Stitch MCP tools, integrate the generated page into site/public, update .stitch/SITE.md and .stitch/metadata.json, and write a new .stitch/next-prompt.md to continue the loop.

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 website page generation using a baton prompt workflow?

Autonomous website page generation uses a baton file to coordinate successive agent iterations, reading a task prompt, generating a screen via Stitch MCP APIs, integrating assets into the site, and writing the next task to continue the loop.

What do I need to set up before starting an autonomous Stitch site-building loop?

You need access to Stitch MCP tools, a DESIGN.md for design context, a SITE.md for site context, and a .stitch/next-prompt.md baton file to initiate the autonomous site-building loop.

How do I integrate generated Stitch HTML screens into my existing site's public folder?

Integration involves downloading the HTML and screenshots from Stitch MCP, moving the HTML into the site's public folder, fixing asset paths, and updating site navigation and documentation.

Can I use Chrome DevTools MCP for visual verification during autonomous site expansion?

Yes, optional Chrome DevTools MCP tools support automated rendering and screenshot comparisons for visual verification when available in your autonomous site-building workflow.

How does the project state management track generated screens and sitemap progress?

Project state management persists a .stitch/metadata.json map of project and screen identifiers, enforcing sitemap and roadmap checks to maintain continuous progress across iterations.