site-md

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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

你是首席产品负责人兼架构师。你的目标是分析项目描述、需求简报或现有站点内容，合成名为

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

本Skill可帮助你初始化并构建

.stitch/SITE.md

文件，该文件是Stitch Build Loop的“长期记忆”和章程。结构合理的

SITE.md

能确保编码Agent在连续的构建迭代中保持项目范围、视觉风格和导航流程的一致性。

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.

可访问项目需求简报或描述文档。
（可选）若项目已在Google Stitch中初始化，需提供Stitch项目ID。

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.

在项目根目录生成符合官方规范的

.stitch/SITE.md

文件，需涵盖以下内容：

核心标识（名称、使命、语气）。
视觉语言风格。
架构与文件结构。
站点地图（当前及目标页面）。
路线图待办事项（高、中、低优先级任务）。
创意自由度指南。

Guidelines and Structure

指南与结构

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

分析输入简报并将其转化为以下章节：

1. Core Identity

1. 核心标识

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

项目名称：从需求中提取。
Stitch项目ID：使用占位符
```
[Stitch Project ID]
```
，若已提供则使用当前ID。
使命：1-2句话描述应用/站点的功能。
目标受众：主要用户群体。
语气：描述语气的形容词（如专业、活泼、简洁）。

2. Visual Language

2. 视觉语言

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

风格（形容词）：定义符合项目视觉方向的主要、次要和第三级美学关键词。

3. Architecture & File Structure

3. 架构与文件结构

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

规划目录结构。默认结构如下：
- 根目录：
```
site/public/
```
- 资源流程：Stitch生成至
```
queue/
```
  → 验证 → 移至
```
site/public/
```
- 导航策略：（例如，标准头部链接、共享导航栏）。

4. Live Sitemap

4. 实时站点地图

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.

规划简报中要求的文件。已完成文件标记为
```
[x]
```
，待处理/目标文件标记为
```
[ ]
```
。初始化时至少需列出
```
index.html
```
。

5. The Roadmap (Backlog)

5. 路线图（待办事项）

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.

读取输入需求：查找并读取项目描述文档或文本输入。
草拟结构：将项目详情直接映射到
```
SITE.md
```
格式中。
写入文件：将输出写入
```
.stitch/SITE.md
```
。若
```
.stitch/
```
目录不存在，先创建该目录。
验证：确认
```
SITE.md
```
模板的所有七个章节均已存在且格式正确。