Stitch Utilities

Skill 14 of 16

Site Md

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

2 minutes · 386 words · 11 sections

Install

$ npx skills add google-labs-code/stitch-skills --skill site-md

$ npx skills add google-labs-code/stitch-skills

» /plugin marketplace add google-labs-code/stitch-skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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:

Core Identity (Name, Mission, Voice).
Visual Language Vibe.
Architecture & File Structure.
Sitemap (Current and target pages).
Roadmap Backlog (High, Medium, Low priority tasks).
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

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

About this skill

Allowed tools: ReadWriteweb_fetch
Source: plugins/stitch-utilities/skills/site-md/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/google-labs-code/stitch-skills, branch main, last pushed 17 August 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

16 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 3 distinct layouts observed: plugins/stitch-build/skills/*/SKILL.md, plugins/stitch-design/skills/*/SKILL.md, plugins/stitch-utilities/skills/*/SKILL.md.

Issue colours

Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “11 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

16 editorial notes across 8 of 16 skills. They are printed in the margin of each skill rather than as errors here.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .agents/plugins/marketplace.json, declaring 3 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /google-labs-code/stitch-skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Stitch SITE.md Skill

Access to a project requirements brief or description document.

Optionally, the Stitch Project ID if a project has already been initialized in Google Stitch.

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

Core Identity (Name, Mission, Voice).

Visual Language Vibe.

Architecture & File Structure.

Sitemap (Current and target pages).

Roadmap Backlog (High, Medium, Low priority tasks).

Creative Freedom Guidelines.

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

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).

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

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).

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.

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.

Read input requirements: Locate and read the project description document or text input.

Draft the structure: Map the project details directly into the SITE.md format.

Write the file: Write the output to .stitch/SITE.md. If the .stitch/ directory does not exist, create it first.

Validate: Verify that all seven sections of the SITE.md template are present and properly formatted.