Index of every page on this site: llms.txt
All skills
google-labs-code avatar

/site-md

@4cf4db8 official
Run it yourself

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

Use this Skill: https://skilld.dev/gh/google-labs-code/stitch-skills/site-md

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈34 tokens for metadata: the name and description. ≈729 when used: this file.

Description uses 1.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈137 characters, or 1.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    The skill synthesizes project requirements into a documentation file (SITE.md). It does not contain malicious code, obfuscation, or high-risk command execution patterns.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 4cf4db8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 3 months ago
What it can do
Reads files Edits files
All 3 allowed tools
ReadWriteweb_fetch

README badge

README badge for google-labs-code/stitch-skills/site-md