Stitch DESIGN.md From Project
This skill is a catalog-normalized import from https://github.com/google-labs-code/stitch-skills at commit 7b53207b94e62911777d53d4238b5f8c88c2b519, source path plugins/stitch-utilities/skills/design-md. The upstream control file was corrected for this workspace: the verified Stitch MCP surface here is design-system oriented, so screen lookup, screen generation, and screen editing tools must be used only when the current host explicitly exposes them.
When to Use This Skill
- Use when existing Stitch screens, screenshots, HTML, or metadata should become a DESIGN.md source of truth.
- The task involves Google Stitch project IDs,
.stitch/ artifacts, DESIGN.md files, Stitch exports, or Stitch-specific validation.
- The broader
stitch-design router points here as the narrowest workflow.
Workflow
- Gather screenshots, exported HTML, design-system metadata, user descriptions, or host-listed screen retrieval output.
- Do not assume this workspace exposes
list_projects, list_screens, get_screen, or get_project.
- Extract atmosphere, palette, typography, shape, elevation, components, layout, responsive behavior, and interaction states.
- Translate CSS/Tailwind into descriptive names with exact values.
- Write
.stitch/DESIGN.md with project title and reusable prompting language.
- Hand off to
stitch-manage-design-system for upload.
Local Assets
examples/, resources/, references/, or reference/ are upstream support material when present. Treat SKILL.md as the source of truth if a support file mentions an unavailable MCP tool.
scripts/ are optional helpers. On Windows, prefer PowerShell or Node equivalents unless Git Bash or WSL is actually available.
- Keep generated
.stitch/ files out of commits unless the user explicitly wants them as durable examples.
Corrected Stitch MCP Surface
Verified in this workspace on 2026-06-15: create_project, upload_design_md, create_design_system_from_design_md, list_design_systems, and apply_design_system. This 2026-07-29 source refresh did not re-verify a broader live MCP surface. Do not claim list_projects, list_screens, get_project, get_screen, generate_screen_from_text, edit_screens, or generate_variants were used unless the current host exposes those exact tools in the active tool list.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/stitch-design-md and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Stitch MCP
- Fallback prompt: "Use the Stitch DESIGN.md From Project skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use local
.stitch/ artifacts, exported HTML or screenshots, bundled scripts, and the Stitch web UI when the host does not expose the needed Stitch MCP operation.
- Do not claim screen lookup, generation, editing, or variant MCP calls unless those tools are present in the active host tool list.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Claiming a Stitch screen-generation, screen-editing, or screen-retrieval MCP call succeeded when the active host does not expose that tool.
- Uploading files, screenshots, HTML, markdown, or design assets to Stitch without user-approved destination and artifact details.
- Reading, printing, storing, or committing Stitch API keys, MCP config secrets, cookies, or credential-bearing files.
- Treating generated design or code as final without local render, syntax, or artifact verification.
- Collapsing this workflow into a broader frontend/design skill when Stitch-specific files, project IDs, or design-system assets matter.
Verification Protocol
Before claiming this skill was applied successfully:
- Pass/fail: The DESIGN.md is grounded in real exports or labeled user-provided descriptions.
- Pass/fail: Major tokens include semantic role and exact value where available.
- Pass/fail: The document avoids implementation-only jargon.
- Pass/fail: The next action is clear: upload, web UI use, or local prompt use.
- Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable.
- Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior.
Related Skills
1---
2name: stitch-design-md
3version: "2.0"
4last_updated: 2026-09-08
5tags: [stitch, design-system, design-md, tokens, mcp]
6description: "Analyze existing Stitch project evidence and synthesize a semantic DESIGN.md for consistent future Stitch generation."
7license: "Apache-2.0"
8metadata:
9 source: https://skillmd.com/skills/practicalswan/stitch-design-md
10---
11
12# Stitch DESIGN.md From Project
13
14This skill is a catalog-normalized import from `https://github.com/google-labs-code/stitch-skills` at commit `7b53207b94e62911777d53d4238b5f8c88c2b519`, source path `plugins/stitch-utilities/skills/design-md`. The upstream control file was corrected for this workspace: the verified Stitch MCP surface here is design-system oriented, so screen lookup, screen generation, and screen editing tools must be used only when the current host explicitly exposes them.
15
16## When to Use This Skill
17
18- Use when existing Stitch screens, screenshots, HTML, or metadata should become a DESIGN.md source of truth.
19- The task involves Google Stitch project IDs, `.stitch/` artifacts, DESIGN.md files, Stitch exports, or Stitch-specific validation.
20- The broader `stitch-design` router points here as the narrowest workflow.
21
22## Workflow
23
241. Gather screenshots, exported HTML, design-system metadata, user descriptions, or host-listed screen retrieval output.
252. Do not assume this workspace exposes `list_projects`, `list_screens`, `get_screen`, or `get_project`.
263. Extract atmosphere, palette, typography, shape, elevation, components, layout, responsive behavior, and interaction states.
274. Translate CSS/Tailwind into descriptive names with exact values.
285. Write `.stitch/DESIGN.md` with project title and reusable prompting language.
296. Hand off to `stitch-manage-design-system` for upload.
30
31## Local Assets
32
33- `examples/`, `resources/`, `references/`, or `reference/` are upstream support material when present. Treat `SKILL.md` as the source of truth if a support file mentions an unavailable MCP tool.
34- `scripts/` are optional helpers. On Windows, prefer PowerShell or Node equivalents unless Git Bash or WSL is actually available.
35- Keep generated `.stitch/` files out of commits unless the user explicitly wants them as durable examples.
36
37## Corrected Stitch MCP Surface
38
39Verified in this workspace on 2026-06-15: `create_project`, `upload_design_md`, `create_design_system_from_design_md`, `list_design_systems`, and `apply_design_system`. This 2026-07-29 source refresh did not re-verify a broader live MCP surface. Do not claim `list_projects`, `list_screens`, `get_project`, `get_screen`, `generate_screen_from_text`, `edit_screens`, or `generate_variants` were used unless the current host exposes those exact tools in the active tool list.
40
41<!-- MCP:START -->
42
43<!-- PORTABILITY:START -->
44## Cross-Client Portability
45
46This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
47
48- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
49 workflow in project instructions when folder discovery is unavailable.
50- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
51- Codex: install or sync the folder into
52 `$CODEX_HOME/skills/stitch-design-md` and restart Codex after major changes.
53
54<!-- PORTABILITY:END -->
55
56## MCP Availability And Fallback
57
58Preferred MCP Server: Stitch MCP
59
60- Fallback prompt: "Use the Stitch DESIGN.md From Project skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
61- Use local `.stitch/` artifacts, exported HTML or screenshots, bundled scripts, and the Stitch web UI when the host does not expose the needed Stitch MCP operation.
62- Do not claim screen lookup, generation, editing, or variant MCP calls unless those tools are present in the active host tool list.
63- Do not claim an MCP operation was used when the active host does not expose it.
64
65<!-- MCP:END -->
66
67## Anti-Patterns
68
69- Claiming a Stitch screen-generation, screen-editing, or screen-retrieval MCP call succeeded when the active host does not expose that tool.
70- Uploading files, screenshots, HTML, markdown, or design assets to Stitch without user-approved destination and artifact details.
71- Reading, printing, storing, or committing Stitch API keys, MCP config secrets, cookies, or credential-bearing files.
72- Treating generated design or code as final without local render, syntax, or artifact verification.
73- Collapsing this workflow into a broader frontend/design skill when Stitch-specific files, project IDs, or design-system assets matter.
74
75## Verification Protocol
76
77Before claiming this skill was applied successfully:
78
791. Pass/fail: The DESIGN.md is grounded in real exports or labeled user-provided descriptions.
802. Pass/fail: Major tokens include semantic role and exact value where available.
813. Pass/fail: The document avoids implementation-only jargon.
824. Pass/fail: The next action is clear: upload, web UI use, or local prompt use.
835. Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable.
846. Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior.
85
86## Related Skills
87
88- [stitch-extract-design-md](../stitch-extract-design-md/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
89- [stitch-manage-design-system](../stitch-manage-design-system/SKILL.md): Use when the task also needs this adjacent Stitch workflow.
90- [stitch-taste-design](../stitch-taste-design/SKILL.md): Use when the task also needs this adjacent Stitch workflow.