stitch-loop

Generate Stitch-driven pages iteratively using next-prompt.md baton management.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/phuchau26/giatsay --skill stitch-loop-phuchau26
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/phuchau26/giatsay/tree/main/skills/stitch-loop
Command: npx skills add https://github.com/phuchau26/giatsay --skill stitch-loop-phuchau26

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables autonomous, iterative frontend site construction by orchestrating Stitch-driven pages through a baton-passing loop, reducing manual coordination and accelerating multi-page development.

Core Features & Use Cases

  • Baton-driven iterations: reads the baton file next-prompt.md, generates a page with Stitch, and schedules the next task.
  • Site integration: moves generated assets into site/public and updates navigation and sitemap consistently.
  • Composable workflow: works with DESIGN.md and SITE.md to enforce design system, roadmap, and architecture; supports chaining to other agents or tools.

Quick Start

Install and run the stitch-loop skill, then begin by populating next-prompt.md with the first baton and design system block.

Frequently Asked Questions about stitch-loop

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

FAQPage Schema
How do I automate multi-page website generation with sequential agent tasks?

You can automate multi-page website generation by orchestrating a baton-passing loop that reads the next-prompt.md file, generates a page using Stitch, and schedules the next task automatically.

What is a baton loop for autonomous front-end builds?

A baton loop for autonomous front-end builds is an iterative orchestration pattern where tasks are sequentially handed to agents via a next-prompt.md file, enabling continuous page generation without manual coordination.

Do I need a DESIGN.md and SITE.md file to use autonomous site generation?

Yes, you need DESIGN.md and SITE.md files to enforce the design system, roadmap, and architecture constraints during autonomous site generation, ensuring generated pages adhere to project specifications.

Can I chain Stitch-driven page generation with other agents or tools?

Yes, the composable workflow supports chaining Stitch-driven page generation to other agents or tools, allowing you to extend the baton-passing loop with additional processing steps.

How does the baton loop update site navigation and sitemap after page generation?

After generating a page, the baton loop moves assets into site/public and consistently updates both the site navigation and sitemap to reflect the newly added content.

What's the best way to start an iterative front-end site construction loop?

To start iterative front-end site construction, populate the next-prompt.md file with your first baton and design system block, then run the skill to begin the autonomous generation cycle.