Stitch Build Loop

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/stitch-loop

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Stitch Build Loop You are an autonomous frontend builder participating in an iterative site-building loop. Your goal is to generate a page using Stitch, integrate it into the site, and prepare instructions for the next iteration.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, The Baton System, Execution Protocol, Orchestration Options, Design System Integration, Common Pitfalls.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• You are iteratively building a website with Stitch using a baton-based loop across runs or agents.
• Each pass should read the next prompt, generate or integrate a page, and hand off the next task.
• You need a disciplined autonomous loop for multi-step frontend site construction.
• Use when the request clearly matches the imported source intent: Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

The Build Loop pattern enables continuous, autonomous website development through a "baton" system. Each iteration:

1. Reads the current task from a baton file (

   .stitch/next-prompt.md

   )
2. Generates a page using Stitch MCP tools
3. Integrates the page into the site structure
4. Writes the next task to the baton file for the next iteration

Imported: Prerequisites

Required:

• Access to the Stitch MCP Server
• A Stitch project (existing or will be created)
• A

  .stitch/DESIGN.md

  file (generate one using the

  design-md

  skill if needed)
• A

  .stitch/SITE.md

  file documenting the site vision and roadmap

Optional:

• Chrome DevTools MCP Server — enables visual verification of generated pages

Examples

Example 1: Ask for the upstream workflow directly

Use @stitch-loop to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @stitch-loop against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @stitch-loop for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @stitch-loop using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/stitch-loop

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Imported Troubleshooting Notes

Imported: Troubleshooting

.stitch/DESIGN.md

.stitch/next-prompt.md

Related Skills

• @server-management

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @service-mesh-expert

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @service-mesh-observability

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @sexual-health-analyzer

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: File Structure Reference

project/
├── .stitch/
│   ├── metadata.json   # Stitch project & screen IDs (persist this!)
│   ├── DESIGN.md       # Visual design system (from design-md skill)
│   ├── SITE.md         # Site vision, sitemap, roadmap
│   ├── next-prompt.md  # The baton — current task
│   └── designs/        # Staging area for Stitch output
│       ├── {page}.html
│       └── {page}.png
└── site/public/        # Production pages
    ├── index.html
    └── {page}.html

.stitch/metadata.json

Schema

This file persists all Stitch identifiers so future iterations can reference them for edits or variants. Populate it by calling

[prefix]:get_project

{
  "name": "projects/6139132077804554844",
  "projectId": "6139132077804554844",
  "title": "My App",
  "visibility": "PRIVATE",
  "createTime": "2026-03-04T23:11:25.514932Z",
  "updateTime": "2026-03-04T23:34:40.400007Z",
  "projectType": "PROJECT_DESIGN",
  "origin": "STITCH",
  "deviceType": "MOBILE",
  "designTheme": {
    "colorMode": "DARK",
    "font": "INTER",
    "roundness": "ROUND_EIGHT",
    "customColor": "#40baf7",
    "saturation": 3
  },
  "screens": {
    "index": {
      "id": "d7237c7d78f44befa4f60afb17c818c1",
      "sourceScreen": "projects/6139132077804554844/screens/d7237c7d78f44befa4f60afb17c818c1",
      "x": 0,
      "y": 0,
      "width": 390,
      "height": 1249
    },
    "about": {
      "id": "bf6a3fe5c75348e58cf21fc7a9ddeafb",
      "sourceScreen": "projects/6139132077804554844/screens/bf6a3fe5c75348e58cf21fc7a9ddeafb",
      "x": 549,
      "y": 0,
      "width": 390,
      "height": 1159
    }
  },
  "metadata": {
    "userRole": "OWNER"
  }
}

name

projects/{id}

projectId

create_project

get_project

title

designTheme

deviceType

MOBILE

DESKTOP

TABLET

screens

id

sourceScreen

x

y

width

height

metadata.userRole

OWNER

EDITOR

VIEWER

Imported: The Baton System

The

.stitch/next-prompt.md

---
page: about
---
A page describing how jules.top tracking works.

**DESIGN SYSTEM (REQUIRED):**
[Copy from .stitch/DESIGN.md Section 6]

**Page Structure:**
1. Header with navigation
2. Explanation of tracking methodology
3. Footer with links

Critical rules:

• The

  page

  field in YAML frontmatter determines the output filename
• The prompt content must include the design system block from

  .stitch/DESIGN.md

• You MUST update this file before completing your work to continue the loop

Imported: Execution Protocol

Step 1: Read the Baton

Parse

.stitch/next-prompt.md

• Page name from the

  page

  frontmatter field
• Prompt content from the markdown body

Step 2: Consult Context Files

Before generating, read these files:

.stitch/SITE.md

.stitch/DESIGN.md

Important checks:

• Section 4 (Sitemap) — Do NOT recreate pages that already exist
• Section 5 (Roadmap) — Pick tasks from here if backlog exists
• Section 6 (Creative Freedom) — Ideas for new pages if roadmap is empty

Step 3: Generate with Stitch

Use the Stitch MCP tools to generate the page:

1. Discover namespace: Run

   list_tools

   to find the Stitch MCP prefix
2. Get or create project:
   • If

     .stitch/metadata.json

     exists, use the

     projectId

     from it
   • Otherwise, call

     [prefix]:create_project

     , then call

     [prefix]:get_project

     to retrieve full project details, and save them to

     .stitch/metadata.json

     (see schema below)
   • After generating each screen, call

     [prefix]:get_project

     again and update the

     screens

     map in

     .stitch/metadata.json

     with each screen's full metadata (id, sourceScreen, dimensions, canvas position)
3. Generate screen: Call

   [prefix]:generate_screen_from_text

   with:

   • projectId

     : The project ID

   • prompt

     : The full prompt from the baton (including design system block)

   • deviceType

     :

     DESKTOP

     (or as specified)
4. Retrieve assets: Before downloading, check if

   .stitch/designs/{page}.html

   and

   .stitch/designs/{page}.png

   already exist:
   • If files exist: Ask the user whether to refresh the designs from the Stitch project or reuse the existing local files. Only re-download if the user confirms.
   • If files do not exist: Proceed with download:

     • htmlCode.downloadUrl

       — Download and save as

       .stitch/designs/{page}.html

     • screenshot.downloadUrl

       — Append

       =w{width}

       to the URL before downloading, where

       {width}

       is the

       width

       value from the screen metadata (Google CDN serves low-res thumbnails by default). Save as

       .stitch/designs/{page}.png

Step 4: Integrate into Site

1. Move generated HTML from

   .stitch/designs/{page}.html

   to

   site/public/{page}.html

2. Fix any asset paths to be relative to the public folder
3. Update navigation:
   • Find existing placeholder links (e.g.,

     href="#"

     ) and wire them to the new page
   • Add the new page to the global navigation if appropriate
4. Ensure consistent headers/footers across all pages

Step 4.5: Visual Verification (Optional)

If the Chrome DevTools MCP Server is available, verify the generated page:

1. Check availability: Run

   list_tools

   to see if

   chrome*

   tools are present
2. Start dev server: Use Bash to start a local server (e.g.,

   npx serve site/public

   )
3. Navigate to page: Call

   [chrome_prefix]:navigate

   to open

   http://localhost:3000/{page}.html

4. Capture screenshot: Call

   [chrome_prefix]:screenshot

   to capture the rendered page
5. Visual comparison: Compare against the Stitch screenshot (

   .stitch/designs/{page}.png

   ) for fidelity
6. Stop server: Terminate the dev server process

Note: This step is optional. If Chrome DevTools MCP is not installed, skip to Step 5.

Step 5: Update Site Documentation

Modify

.stitch/SITE.md

• Add the new page to Section 4 (Sitemap) with

  [x]

• Remove any idea you consumed from Section 6 (Creative Freedom)
• Update Section 5 (Roadmap) if you completed a backlog item

Step 6: Prepare the Next Baton (Critical)

You MUST update

.stitch/next-prompt.md

1. Decide the next page:
   • Check

     .stitch/SITE.md

     Section 5 (Roadmap) for pending items
   • If empty, pick from Section 6 (Creative Freedom)
   • Or invent something new that fits the site vision
2. Write the baton with proper YAML frontmatter:

---
page: achievements
---
A competitive achievements page showing developer badges and milestones.

**DESIGN SYSTEM (REQUIRED):**
[Copy the entire design system block from .stitch/DESIGN.md]

**Page Structure:**
1. Header with title and navigation
2. Badge grid showing unlocked/locked states
3. Progress bars for milestone tracking

Imported: Orchestration Options

The loop can be driven by different orchestration layers:

.stitch/next-prompt.md

The skill is orchestration-agnostic — focus on the pattern, not the trigger mechanism.

Imported: Design System Integration

This skill works best with the

design-md

1. First time setup: Generate

   .stitch/DESIGN.md

   using the

   design-md

   skill from an existing Stitch screen
2. Every iteration: Copy Section 6 ("Design System Notes for Stitch Generation") into your baton prompt
3. Consistency: All generated pages will share the same visual language

Imported: Common Pitfalls

• ❌ Forgetting to update

  .stitch/next-prompt.md

  (breaks the loop)
• ❌ Recreating a page that already exists in the sitemap
• ❌ Not including the design system block from

  .stitch/DESIGN.md

  in the prompt
• ❌ Leaving placeholder links (

  href="#"

  ) instead of wiring real navigation
• ❌ Forgetting to persist

  .stitch/metadata.json

  after creating a new project

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.