stitch-loop

Coordinate baton-driven Stitch workflows to generate and integrate web pages.

Updated Mar 29, 2025
One-click install
npx skills add https://github.com/ketzal88/gym-counter --skill stitch-loop-ketzal88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/ketzal88/gym-counter/tree/main/.claude/skills/stitch-loop
Command: npx skills add https://github.com/ketzal88/gym-counter --skill stitch-loop-ketzal88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables autonomous, baton-driven web page creation and integration using Stitch, reducing manual coordination to a repeatable loop.

Core Features & Use Cases

  • Baton System: Read the next task from the baton file next-prompt.md, generate a page with Stitch MCP tools, and integrate it into the site structure.
  • Iterative Autonomy: Each iteration passes control to the next task, enabling continuous frontend development without direct human intervention.
  • Site Integration & Handoff: Move generated pages into the site, wire navigation, and prepare the next baton prompt for subsequent work.

Quick Start

Place the initial baton task in next-prompt.md and run the Stitch loop to generate a page and write the next baton for the following 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 frontend site-building without manual intervention?

An autonomous, baton-driven workflow coordinates iterative frontend site-building by reading next-prompt.md, generating pages with Stitch MCP tools, integrating results into the site structure, and writing the next instruction for the following iteration.

What is a baton-driven workflow for web page generation and integration?

A baton-driven workflow for web page generation uses a prompt file to pass control between iterations. The agent reads the current task, generates a page with Stitch MCP tools, integrates it, and writes the next baton prompt for subsequent work.

Do I need a Stitch server and context files to run the autonomous site-building loop?

Yes, running the autonomous site-building loop requires a Stitch server, DESIGN.md and SITE.md context files for design rules and sitemap, and a baton-driven prompt file like next-prompt.md to guide each iteration.

How do I start an iterative site-building loop using Stitch MCP tools?

Place the initial baton task in next-prompt.md and run the Stitch loop. The agent reads the baton file, generates a page with Stitch MCP tools, integrates the result into the site structure, and writes the next instruction for the following iteration.

How does the Stitch loop handle site integration and page handoff between iterations?

The Stitch loop handles site integration and page handoff by moving generated pages into the site, wiring navigation, and writing the next baton prompt for the following iteration to continue iterative frontend development autonomously.