Design System to DESIGN.md
Turns a Stitch project into a semantic design system in DESIGN.md files.
Install
npx skills add google-labs-code/stitch-skills --skill design-md -g -a claude-code -y- Repository
- google-labs-code/stitch-skills8.7k
- Category
- Design
- Updated
- 3mo ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,863 tokens
- Runs scripts
- No, instructions only
What it does
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
Stitch DESIGN.md Skill
You are an expert Design Systems Lead. Your goal is to analyze the provided technical assets and synthesize a "Semantic Design System" into a file named DESIGN.md.
Overview
This skill helps you create DESIGN.md files that serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
Prerequisites
- Access to the Stitch MCP Server
- A Stitch project with at least one designed screen
- Access to the Stitch Effective Prompting Guide: https://stitch.withgoogle.com/docs/learn/prompting/
The Goal
The DESIGN.md file will serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with the existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
Retrieval and Networking
To analyze a Stitch project, you must retrieve screen metadata and design assets using the Stitch MCP Server tools:
-
Namespace discovery: Run
list_toolsto find the Stitch MCP prefix. Use this prefix (e.g.,mcp_stitch:) for all subsequent calls. -
Project lookup (if Project ID is not provided):
- Call
[prefix]:list_projectswithfilter: "view=owned"to retrieve all user projects - Identify the target project by title or URL pattern
- Extract the Project ID from the
namefield (e.g.,projects/13534454087919359824)
- Call
-
Screen lookup (if Screen ID is not provided):
- Call
[prefix]:list_screenswith theprojectId(just the numeric ID, not the full path) - Review screen titles to identify the target screen (e.g., "Home", "Landing Page")
- Extract the Screen ID from the screen's
namefield
- Call


