stitch-loop

Automate iterative frontend page creation with Stitch via a baton loop.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/BoraPerusic/agents --skill stitch-loop-boraperusic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stitch-loop
Source: https://github.com/BoraPerusic/agents/tree/main/skills/to%20try/stitch-loop
Command: npx skills add https://github.com/BoraPerusic/agents --skill stitch-loop-boraperusic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of building and deploying iterative frontend pages using Stitch, enabling autonomous agents to collaborate via a baton-passing loop.

Core Features & Use Cases

  • Baton-based autonomic site construction: read the current task from .stitch/next-prompt.md, generate a page with Stitch MCP tools, and integrate it into the site structure, then write the next task back to the baton.
  • Context-aware orchestration: consult .stitch/SITE.md and .stitch/DESIGN.md to respect project scope, design system, sitemap, and roadmap.
  • End-to-end workflow coordination: persist metadata in .stitch/metadata.json after project creation and screen generation, and update site navigation.

Quick Start

Read the baton from .stitch/next-prompt.md, generate the page with Stitch, and write the next task back to the baton.

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 construction with a baton loop?▼

Iterative frontend site construction is automated by reading prompts from .stitch/next-prompt.md, generating pages with Stitch MCP tools, and writing the next task back to the baton file for autonomous multi-step workflows.

How does a baton-based loop work for autonomous page generation?▼

A baton-based loop works by reading the current task from .stitch/next-prompt.md, generating the requested page, integrating it into the site structure, and then updating the baton file with the next prompt to continue the cycle.

Do I need specific context files to generate pages with Stitch MCP tools?▼

Yes, page generation requires reading project context from .stitch/SITE.md and .stitch/DESIGN.md to respect the defined project scope, design system, sitemap, and roadmap during the iterative build process.

What is the best way to manage design tokens during iterative website development?▼

Managing design tokens during iterative development is handled by consulting .stitch/DESIGN.md for the design system, applying tokens during page generation, and persisting project state in .stitch/metadata.json after creation.

Can I use this approach for multi-step page creation workflows across iterations?▼

Yes, this approach is designed specifically for multi-step page creation workflows across iterations, coordinating end-to-end tasks like updating site navigation and persisting metadata after each screen generation cycle.

Why does my autonomous site build fail to maintain project scope and design consistency?▼

Autonomous site builds fail to maintain scope when the workflow does not consult .stitch/SITE.md and .stitch/DESIGN.md, which are required to read project context, manage design tokens, and update navigation properly.