stitch::manage-design-system
Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.
Install / Use
npx skills add google-labs-code/stitch-skills --skill manage-design-systemInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Our assessment of stitch::manage-design-system
stitch::manage-design-system scores 84/100 on our quality scale, 189th of 260 Design skills we index.
Its SKILL.md is 5.5 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.
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-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
stitch::manage-design-system compared with similar skills
All 4 of these similar skills score higher than stitch::manage-design-system; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stitch::manage-design-system (this skill)by google-labs-code | 84 | 8.4k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install stitch::manage-design-system?
- Run
npx skills add google-labs-code/stitch-skills --skill "stitch::manage-design-system". The install tabs above show the steps for each supported agent. - Which AI agents does stitch::manage-design-system 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 stitch::manage-design-system 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 stitch::manage-design-system 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: stitch::manage-design-system description: >- Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens. allowed-tools:
- "stitch*:*"
- "Bash"
- "Read"
- "Write"
- "web_fetch"
Design-System
Create a "source of truth" for your project's design language to ensure consistency across all future screens.
[!NOTE] Refer to your system prompt for instruction on handling MCP tool prefixes for all tools mentioned in this skill (e.g.,
get_screen,create_design_system_from_design_md,apply_design_system).
📥 Retrieval
To analyze a Stitch project, you must retrieve metadata and assets using the Stitch MCP tools:
- Project lookup: Use
list_projectsto find the targetprojectId. - Screen lookup: Use
list_screensfor thatprojectIdto find representative screens (e.g., "Home", "Main Dashboard"). - Metadata fetch: Call
get_screenfor the target screen to getscreenshot.downloadUrlandhtmlCode.downloadUrl. - Asset download: Use
read_url_contentto fetch the HTML code.
🧠 Synthesis from Description
If you need to extract a design system from existing screens, use the design-md skill (in the stitch-utilities plugin).
If there are no existing screens (new project), or the user provides a direct description (e.g., "dark theme, blue and purple, rounded, Inter font"):
- Map the user's vague terms to precise values using the design mappings (see
design-mdskill institch-utilitiesorgenerate-designskill). - Select concrete hex codes, font families, and roundness values.
- Generate the
DESIGN.mdfile (refer to thedesign-mdskill institch-utilitiesfor structure). - Proceed to the "Create or Update Design System in Stitch" step below.
📝 Output Structure
The DESIGN.md file should follow the structure defined in the design-md skill (in the stitch-utilities plugin).
🚀 Create or Update Design System in Stitch
After generating .stitch/DESIGN.md, make sure to also create or update the
design system in Stitch.
Two-step design system creation:
[!WARNING] Checkpoint — User Confirmation Required. Before uploading, you MUST pause and ask the user for confirmation. Present a summary of the design system you are about to create (display name, key colors, fonts, and roundness) and wait for explicit approval before proceeding. Do NOT upload until the user confirms.
- Upload
DESIGN.md:-
Option A (Recommended - Uploader Script): Use the modified
upload-to-stitchPython script which natively handles.mdfiles. It base64-encodes the markdown file in-process and sends it to the/v1/projects/{projectId}/screens:batchCreateendpoint, bypassing output token limits.python3 stitch-skills/plugins/stitch-design/skills/upload-to-stitch/scripts/upload_to_stitch.py \ --project-id <PROJECT_ID> \ --file-path /path/to/DESIGN.md \ --api-key <API_KEY> \ --generated-by <GENERATED_BY>Set
<GENERATED_BY>to identify the skill or tool that produced theDESIGN.md. Use the calling skill name when invoked from another skill (e.g.stitch::code-to-design), or the agent/tool name for standalone use (e.g.Gemini,Claude Code). If omitted, the script defaults toUserUploadedDesignMd.This returns the
sourceScreenID and thescreenInstanceID. -
Option B (Direct MCP Tool): If the
DESIGN.mdis small (under ~5KB), you can call theupload_design_mdMCP tool directly, passing the base64-encoded design markdown content asdesignMdBase64.
-
- Create Design System: Call the
create_design_system_from_design_mdtool immediately after the upload, passing theprojectIdand theselectedScreenInstance(containing theidandsourceScreenreturned from the upload step).
Once the upload script and create_design_system_from_design_md have both completed,
Stitch holds the design tokens at the project level — you do NOT need to repeat
them in generation prompts.
🎨 Apply Design System to Screens
Use apply_design_system to apply a design system to existing screens.
[!IMPORTANT]
selectedScreenInstancesmust contain onlyidandsourceScreen— do NOT include position/dimension fields (x,y,width,height) or the request will fail with "invalid argument". Get the screen instance IDs fromget_project.
{
"projectId": "...",
"assetId": "...",
"selectedScreenInstances": [
{
"id": "...",
"sourceScreen": "projects/.../screens/..."
}
]
}
How to get the required IDs:
- Call
get_projectto retrievescreenInstances— each has anidandsourceScreen. - Call
list_design_systemsto retrieve the design systemname(format:assets/{assetId}) — use the part afterassets/as theassetId. - Filter out any instances with
type: "DESIGN_SYSTEM_INSTANCE"— only pass real screens.
📋 Update Project Metadata
After writing .stitch/DESIGN.md, also create or update .stitch/metadata.json
to track the projectId, title, all known screens, and design system summary.
See examples/metadata.json for the format.
Schema Reference
See reference/tool-schema.md for the full
designSystem object schema with all available options.
💡 Best Practices
Refer to the design-md skill (in the stitch-utilities plugin) for best practices on describing design elements.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
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.
