stitch-loop

Orchestrate iterative Stitch site construction with baton-based task handoffs.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/seflless/dot-agents --skill stitch-loop-seflless
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/seflless/dot-agents/tree/main/skills/stitch-loop
Command: npx skills add https://github.com/seflless/dot-agents --skill stitch-loop-seflless

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables autonomous frontend builders and agents to iteratively build, validate, and deploy pages into a Stitch project using a baton-passing loop.

Core Features & Use Cases

  • Iterative page generation: Generate, validate, and integrate a new page into the site structure across iterations.
  • Baton-passing orchestration: Read a baton file to obtain the next task, then write the next task for the subsequent iteration.
  • Prerequisite-driven workflow: Requires a Stitch server, a DESIGN.md for style, and a SITE.md for project context.
  • Use Case: An agent starts with a basic homepage, then incrementally adds pages and features while keeping global navigation consistent.

Quick Start

Provide the initial baton prompt in next-prompt.md to start the first Stitch-driven page build.

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 web page generation and site building?

A baton-passing loop drives iterative page generation by reading a baton file to obtain the next task, then writing the next task for the subsequent iteration. This orchestrates autonomous site construction across successive build cycles.

What do I need to set up before starting an autonomous Stitch site build?

Prerequisites for a Stitch site build include a running Stitch server, a DESIGN.md file for style guidelines, and a SITE.md file for project context. You must also provide the initial baton prompt in next-prompt.md to start the first page build.

How does baton-based task handoff work for frontend web development?

Baton-based task handoff reads a baton file to obtain the current page generation task, executes the design and integration, then writes the next task for the subsequent iteration. This loop advances the sitemap incrementally across web development cycles.

Can I incrementally add pages to a web project while keeping navigation consistent?

Yes, an autonomous iterative building loop lets you incrementally add pages and features while keeping global navigation consistent. The agent starts with a basic homepage and advances the site structure through successive validated iterations.

What is the best way to validate and integrate new pages into an existing sitemap?

Using an autonomous orchestration loop that drives page generation, validation, and integration step-by-step is the best way to integrate new pages into an existing sitemap. It enforces prerequisite project context files to ensure structural consistency across iterations.