What is the site-md skill?
The site-md skill turns a requirements brief into .stitch/SITE.md, the constitution for the Stitch Build Loop. The agent plays product owner and architect, then records the project's identity, visual vibe, architecture, live sitemap and prioritized roadmap so later coding sessions stay aligned.
The skill belongs to the stitch-utilities plugin, and its SKILL.md casts the agent as a Lead Product Owner and Architect. The input is a project description, requirements brief or existing site content, and the output is one file named .stitch/SITE.md.
Its own overview calls SITE.md the long-term memory and constitution for the Stitch Build Loop. A well structured file keeps coding agents aligned on scope, visual vibe and navigation flow across successive build iterations.
What the file records
- Core identity: project name, Stitch project ID or a placeholder, a one to two sentence mission, target audience and voice adjectives.
- Visual language: a primary, secondary and tertiary aesthetic keyword.
- Architecture and file structure, defaulting to site/public as the root and a queue folder that Stitch output passes through before it is validated and moved.
- A live sitemap, with finished files marked [x] and pending files marked [ ], and index.html listed at the start.
The roadmap and the action plan
The backlog splits the brief into concrete tasks. High priority holds core pages, basic layouts and primary user flows. Medium covers interactive features, forms and secondary pages, and low covers enhancements, visual assets and optional states.
- Read the requirements document or text input.
- Draft the structure by mapping the details into the SITE.md format.
- Write .stitch/SITE.md, creating the .stitch folder first if it is missing.
- Validate that every section of the template is present and properly formatted.
Who the site-md skill is for
Best for
- Teams starting a multi-page Stitch build who want scope written down before the first screen.
- Projects run by several agent sessions, where each session needs the same memory of pages done and pending.
- People who already have a brief but no structured plan.
Not for
- Generating screens. The file is a plan, and stitch-loop is the skill that runs the build iterations.
- Documenting a design system. For tokens and styling language, use design-md.
- Rewriting a rough prompt. enhance-prompt is the closer fit.
Use it with UiChemy
SITE.md is a planning file for a Stitch build, not a WordPress artifact. If the finished pages should live in WordPress, UiChemy can bring them in through AI to WordPress, Composer or Figma. Click Get Started on uichemy.com.
How to install Stitch site-md Skill: Write a SITE.md Project Constitution
npx plugins add google-labs-code/stitch-skills --scope project --target claude-codePick your agent
Claude Code users run
npx plugins add google-labs-code/stitch-skills --scope project --target claude-code. Cursor users run the same command with--scope workspace --target cursor.Find the plugin
This skill is in stitch-utilities, not stitch-design or stitch-build. With Codex, add the marketplace using
codex plugin marketplace add google-labs-code/stitch-skills --ref mainand install stitch-utilities.Set up Stitch if you will build
The README lists the Stitch MCP server as a prerequisite for the skill suite, with setup at https://stitch.withgoogle.com/docs/mcp/setup/.
Bring a brief
Have a requirements document or a written description of the site ready for the agent to read.
Check that it loaded
Ask the agent to create a SITE.md from your brief. It should write .stitch/SITE.md with identity, vibe, architecture, a checkbox sitemap that includes index.html, and a roadmap grouped by priority.
Key features
- Constitution fileThe single output is .stitch/SITE.md at the project root, created together with the .stitch folder if it does not exist.
- Core identity sectionRecords the project name, a Stitch project ID or the placeholder text, a short mission, the target audience and tone adjectives such as professional, playful or clean.
- Visual vibe keywordsDefines a primary, secondary and tertiary aesthetic keyword that match the project's visual direction.
- Default architectureSuggests a site/public root and an asset flow where Stitch generates into a queue folder, then output is validated and moved into the public folder.
- Checkbox sitemapLists requested files, with completed pages as [x] and pending pages as [ ], and at least index.html present when the file is first created.
- Prioritized roadmapTurns requirements into tasks grouped as high, medium and low priority, from core layouts down to optional states.
- Creative freedom guidelinesThe goal list includes a section on creative freedom, so later iterations know how far they can depart from the brief.
- Optional Stitch project linkA Stitch project ID is optional input, used if a project has already been initialized in Google Stitch.
- Light tool footprintThe skill's allowed tools are only Read, Write and web_fetch, so it needs no Stitch MCP calls to produce the file.
Frequently asked questions
What is SITE.md?
It is a project constitution file at .stitch/SITE.md. The skill describes it as long-term memory for the Stitch Build Loop, holding the project's identity, visual vibe, file structure, sitemap and roadmap so coding agents stay aligned across successive build iterations.
What input does the skill need?
A project requirements brief or description document is the prerequisite. A Stitch project ID is optional, used if a project already exists in Google Stitch. Without an ID the file carries a placeholder in the project ID field.
How do I install the site-md skill?
Run the repository's plugin install, for example npx plugins add google-labs-code/stitch-skills with a project scope and your agent as the target. Codex users add the repo as a plugin marketplace. The skill ships in the stitch-utilities plugin.
How is the sitemap written?
As a checklist of the files in the brief. Finished files are marked [x] and pending or target files are marked [ ]. At initialization at least index.html must be listed, and the list is meant to stay current as the build moves on.
How does the roadmap rank work?
Requirements become concrete tasks in three groups. High priority covers core pages, basic layouts and primary flows. Medium covers interactive features, forms and secondary pages. Low covers enhancements, visual assets and optional states.
Does site-md generate any screens?
No. It only writes the planning file. Its allowed tools are Read, Write and web_fetch, so it makes no Stitch MCP calls. The build iterations that read the file are the job of other skills in the same repository.
Where does the file structure default come from?
The SKILL.md says to default to site/public as the root, with Stitch generating into a queue folder, then validating and moving files into site/public. The navigation strategy, such as header links or a shared bar, is left for you to state in the file.