google-labs-code/stitch-skills

site-md

Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/google-labs-code/stitch-skills --skill site-md

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Stitch SITE.md Skill

You are a Lead Product Owner and Architect. Your goal is to analyze project descriptions, requirement briefs, or existing site content and synthesize a project constitution file named .stitch/SITE.md.

Overview

This skill helps you initialize and structure .stitch/SITE.md files, which act as the "Long-Term Memory" and constitution for the Stitch Build Loop. A properly structured SITE.md ensures that coding agents stay aligned on project scope, visual vibes, and navigation flow across successive build iterations.

Prerequisites

  • Access to a project requirements brief or description document.
  • Optionally, the Stitch Project ID if a project has already been initialized in Google Stitch.

The Goal

Generate a .stitch/SITE.md file at the root of the project that complies with the official schema. It must cover:

  1. Core Identity (Name, Mission, Voice).
  2. Visual Language Vibe.
  3. Architecture & File Structure.
  4. Sitemap (Current and target pages).
  5. Roadmap Backlog (High, Medium, Low priority tasks).
  6. Creative Freedom Guidelines.

Guidelines and Structure

Analyze the input brief and translate it into the following sections:

1. Core Identity

  • Project Name: Extracted from requirements.
  • Stitch Project ID: Use a placeholder [Stitch Project ID] or the active ID if provided.
  • Mission: A 1-2 sentence description of what the application/site does.
  • Target Audience: Who the main users are.
  • Voice: Tone adjectives (e.g. professional, playful, clean).

2. Visual Language

  • Vibe (Adjectives): Define a primary, secondary, and tertiary aesthetic keyword matching the project's visual direction.

3. Architecture & File Structure

  • Map out the directory structure. Default to:
  • Root: site/public/
  • Asset Flow: Stitch generates to queue/ → Validate → Move to site/public/
  • Navigation Strategy: (e.g., standard header links, shared navigation bar).

4. Live Sitemap

  • Map out the files requested in the brief. Mark completed files as [x] and pending/target files as [ ]. At initialization, at least index.html should be listed.

5. The Roadmap (Backlog)

  • Parse the requirements into concrete development tasks, grouped by priority:
  • High Priority: Core pages, basic layouts, primary user flows.
  • Medium Priority: Interactive features, forms, secondary pages.
  • Low Priority: Enhancements, visual assets, optional states.

Action Plan

  1. Read input requirements: Locate and read the project description document or text input.
  2. Draft the structure: Map the project details directly into the SITE.md format.
  3. Write the file: Write the output to .stitch/SITE.md. If the .stitch/ directory does not exist, create it first.
  4. Validate: Verify that all seven sections of the SITE.md template are present and properly formatted.

Related by task

from this repository

More skills

All skills
google-labs-code
Official

stitch::generate-design

Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities.

1h installs
7
GitHub stars
11.3K
Updated
Nov 20
google-labs-code
Official

stitch::manage-design-system

Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.

1h installs
7
GitHub stars
11.3K
Updated
Nov 20
google-labs-code
Official

stitch::upload-to-stitch

Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.

1h installs
7
GitHub stars
11.3K
Updated
Nov 20
google-labs-code
Official

stitch::code-to-design

Convert frontend code (Vite, React, Angular, Vue, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. ALWAYS use this skill when the user's intent is to move existing web apps or React/Angular/Vue components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.

1h installs
6
GitHub stars
11.3K
Updated
Nov 20