design-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
Install / Use
npx skills add google-labs-code/stitch-skills --skill design-mdInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Our assessment of design-md
design-md scores 84/100 on our quality scale, 190th of 262 Design skills we index.
Its SKILL.md is 7.5 KB long, well organised into 23 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 8,363 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-31 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
design-md compared with similar skills
All 4 of these similar skills score higher than design-md; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| design-md (this skill)by google-labs-code | 84 | 8.4k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
Frequently asked questions
- How do I install design-md?
- Run
npx skills add google-labs-code/stitch-skills --skill design-md. The install tabs above show the steps for each supported agent. - Which AI agents does design-md work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is design-md safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is design-md still maintained?
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: design-md description: Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files allowed-tools:
- "stitch*:*"
- "Read"
- "Write"
- "web_fetch"
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
-
Metadata fetch:
- Call
[prefix]:get_screenwith bothprojectIdandscreenId(both as numeric IDs only) - This returns the complete screen object including:
screenshot.downloadUrl- Visual reference of the designhtmlCode.downloadUrl- Full HTML/CSS source codewidth,height,deviceType- Screen dimensions and target platform- Project metadata including
designThemewith color and style information
- Call
-
Asset download:
- Use
web_fetchorread_url_contentto download the HTML code fromhtmlCode.downloadUrl - Optionally download the screenshot from
screenshot.downloadUrlfor visual reference - Parse the HTML to extract Tailwind classes, custom CSS, and component patterns
- Use
-
Project metadata extraction:
- Call
[prefix]:get_projectwith the projectname(full path:projects/{id}) to get:designThemeobject with color mode, fonts, roundness, custom colors- Project-level design guidelines and descriptions
- Device type preferences and layout principles
- Call
Analysis & Synthesis Instructions
1. Extract Project Identity (JSON)
- Locate the Project Title
- Locate the specific Project ID (e.g., from the
namefield in the JSON)
2. Define the Atmosphere (Image/HTML)
Evaluate the screenshot and HTML structure to capture the overall "vibe." Use evocative adjectives to describe the mood (e.g., "Airy," "Dense," "Minimalist," "Utilitarian").
3. Map the Color Palette (Tailwind Config/JSON)
Identify the key colors in the system. For each color, provide:
- A descriptive, natural language name that conveys its character (e.g., "Deep Muted Teal-Navy")
- The specific hex code in parentheses for precision (e.g., "#294056")
- Its specific functional role (e.g., "Used for primary actions")
4. Translate Geometry & Shape (CSS/Tailwind)
Convert technical border-radius and layout values into physical descriptions:
- Describe
rounded-fullas "Pill-shaped" - Describe
rounded-lgas "Subtly rounded corners" - Describe
rounded-noneas "Sharp, squared-off edges"
5. Describe Depth & Elevation
Explain how the UI handles layers. Describe the presence and quality of shadows (e.g., "Flat," "Whisper-soft diffused shadows," or "Heavy, high-contrast drop shadows").
Output Guidelines
- Language: Use descriptive design terminology and natural language exclusively
- Format: Generate a clean Markdown file following the structure below
- Precision: Include exact hex codes for colors while using descriptive names
- Context: Explain the "why" behind design decisions, not just the "what"
Output Format (DESIGN.md Structure)
# Design System: [Project Title]
**Project ID:** [Insert Project ID Here]
## 1. Visual Theme & Atmosphere
(Description of the mood, density, and aesthetic philosophy.)
## 2. Color Palette & Roles
(List colors by Descriptive Name + Hex Code + Functional Role.)
## 3. Typography Rules
(Description of font family, weight usage for headers vs. body, and letter-spacing character.)
## 4. Component Stylings
* **Buttons:** (Shape description, color assignment, behavior).
* **Cards/Containers:** (Corner roundness description, background color, shadow depth).
* **Inputs/Forms:** (Stroke style, background).
## 5. Layout Principles
(Description of whitespace strategy, margins, and grid alignment.)
Usage Example
To use this skill for the Furniture Collection project:
-
Retrieve project information:
Use the Stitch MCP Server to get the Furniture Collection project -
Get the Home page screen details:
Retrieve the Home page screen's code, image, and screen object information -
Reference best practices:
Review the Stitch Effective Prompting Guide at: https://stitch.withgoogle.com/docs/learn/prompting/ -
Analyze and synthesize:
- Extract all relevant design tokens from the screen
- Translate technical values into descriptive language
- Organize information according to the DESIGN.md structure
-
Generate the file:
- Create
DESIGN.mdin the project directory - Follow the prescribed format exactly
- Ensure all color codes are accurate
- Use evocative, designer-friendly language
- Create
Best Practices
- Be Descriptive: Avoid generic terms like "blue" or "rounded." Use "Ocean-deep Cerulean (#0077B6)" or "Gently curved edges"
- Be Functional: Always explain what each design element is used for
- Be Consistent: Use the same terminology throughout the document
- Be Visual: Help readers visualize the design through your descriptions
- Be Precise: Include exact values (hex codes, pixel values) in parentheses after natural language descriptions
Tips for Success
- Start with the big picture: Understand the overall aesthetic before diving into details
- Look for patterns: Identify consistent spacing, sizing, and styling patterns
- Think semantically: Name colors by their purpose, not just their appearance
- Consider hierarchy: Document how visual weight and importance are communicated
- Reference the guide: Use language and patterns from the Stitch Effective Prompting Guide
Common Pitfalls to Avoid
- ❌ Using technical jargon without translation (e.g., "rounded-xl" instead of "generously rounded corners")
- ❌ Omitting color codes or using only descriptive names
- ❌ Forgetting to explain functional roles of design elements
- ❌ Being too vague in atmosphere descriptions
- ❌ Ignoring subtle design details like shadows or spacing patterns
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
