stitch::generate-design
Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities.
Install / Use
npx skills add google-labs-code/stitch-skills --skill generate-designInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of stitch::generate-design
stitch::generate-design scores 91/100 on our quality scale, 984th of 2,790 Automation skills we index (top 36%).
Its SKILL.md is 11 KB long, well organised into 36 sections with 5 code examples: 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-11-15 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::generate-design compared with similar skills
All 4 of these similar skills score higher than stitch::generate-design; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stitch::generate-design (this skill)by google-labs-code | 91 | 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::generate-design?
- Run
npx skills add google-labs-code/stitch-skills --skill "stitch::generate-design". The install tabs above show the steps for each supported agent. - Which AI agents does stitch::generate-design 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::generate-design 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::generate-design 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::generate-design description: >- Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities. allowed-tools:
- "stitch*:*"
- "Bash"
- "Read"
- "Write"
- "web_fetch"
Generate Design
Create new design screens from text descriptions, images, or mockups, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP.
[!NOTE] Refer to your system prompt for instruction on handling MCP tool prefixes for all tools mentioned in this skill (e.g.,
list_projects,generate_screen_from_text,edit_screens).
🎨 Prompt Enhancement Pipeline
Before calling any Stitch generation or editing tool, you MUST enhance the user's prompt.
1. Analyze Context
- Project: Use
list_projectsto find the correctprojectId. If no suitable project exists, create one usingcreate_project. - Design System: Check if a design system exists for the project via
list_design_systems. If one exists, design tokens (colors, fonts, roundness) are already applied at the project level — do NOT include any color, font, or theme instructions in the generation prompt. If none exists, delegate to the manage-design-system skill first before generating screens.
2. Refine UI/UX Terminology
Consult Design Mappings to replace vague terms.
- Vague: "Make a nice header"
- Professional: "Sticky navigation bar with glassmorphism effect and centered logo"
Use Prompting Keywords for component names, adjective palettes, color roles, and shape descriptions.
3. Structure the Final Prompt
Format the enhanced prompt for Stitch. Focus exclusively on layout, content, and structure — never include colors, fonts, or theme instructions (these are handled by the manage-design-system skill at the project level).
For new screens, use this template:
[Overall purpose and user intent of the page]
**PLATFORM:** [Web/Mobile], [Desktop/Mobile]-first
**PAGE STRUCTURE:**
1. **Header:** [Description of navigation and branding]
2. **Hero Section:** [Headline, subtext, and primary CTA]
3. **Primary Content Area:** [Detailed component breakdown]
4. **Footer:** [Links and copyright information]
For edits, be specific about what to change:
- Location: "Change the [primary button] in the [hero section]..."
- Visuals: "...to a darker blue (#004080) and add a subtle shadow."
- Structure: "Add a secondary button next to the primary one with the text 'Learn More'."
[!CAUTION] Do NOT include hex codes, font names, color palettes, roundness values, or any design system tokens in a generation prompt. These are applied at the project level by the manage-design-system skill and will conflict if duplicated. (For edit prompts, hex codes are acceptable for precise color adjustments.)
4. Present AI Insights
After any tool call, always surface the outputComponents (Text Description and
Suggestions) to the user.
See examples/enhanced-prompt.md for a full before/after prompt enhancement example.
Steps
Determine the Mode
Decide which flow to use based on the user's request:
- User wants to create from a text description → Generate from Text flow
- User provides an image, screenshot, or mockup → Generate from Image flow
- User wants to modify an existing screen → Edit flow
- User wants layout/color/content variations → Generate Variants flow
Generate from Text Flow (New Screen)
1. Enhance the User Prompt
Apply the Prompt Enhancement Pipeline above.
2. Identify the Project
Use list_projects to find the correct projectId if it is not already known.
3. Generate the Screen
Call the generate_screen_from_text tool with the enhanced prompt and the
designSystem ID (if found in Step 1).
{
"projectId": "...",
"prompt": "[Your Enhanced Prompt]",
"designSystem": "assets/...", // Optional: Pass if found in Step 1
"deviceType": "DESKTOP" // Options: MOBILE, DESKTOP, TABLET
}
4. Present AI Feedback
Always show the text description and suggestions from outputComponents to the
user.
5. Download Design Assets
After generation, download the HTML and screenshot urls from outputComponents
to the .stitch/designs directory.
- Naming: Use the screen ID or a descriptive slug for the filename.
- Tools: Use
curl -oviarun_commandor similar. - Directory: Ensure
.stitch/designsexists.
6. Review and Refine
- If the result is not exactly as expected, continue with the Edit flow to make targeted adjustments.
- Do NOT re-generate from scratch unless the fundamental layout is wrong.
Generate from Image Flow (Image/Mockup → Design)
Use this flow when the user provides an image, screenshot, or design mockup to recreate in Stitch.
1. Identify the Project
Use list_projects to find the correct projectId. If no suitable project
exists, create one using create_project.
2. Upload the Image
Delegate to the upload-to-stitch skill to upload the image to the project. This creates a new screen with the image as its content.
3. Refine with Edit
Once uploaded, use list_screens to find the newly created screenId, then
call edit_screens with a descriptive prompt to refine the design:
{
"projectId": "...",
"selectedScreenIds": ["<uploaded-screen-id>"],
"prompt": "[Describe what to adjust, enhance, or recreate from this mockup]"
}
[!TIP] For best results, describe the intent behind the image rather than just saying "make it look like this". For example: "This is a dashboard mockup — recreate it with a proper data table, sidebar navigation, and chart widgets."
4. Present AI Feedback
Always show the text description and suggestions from outputComponents to the
user.
5. Download Design Assets
Download the HTML and screenshot urls from outputComponents to the
.stitch/designs directory.
- Naming: Use the screen ID or a descriptive slug for the filename.
- Tools: Use
curl -oviarun_commandor similar. - Directory: Ensure
.stitch/designsexists.
Edit Flow (Modify Existing Screen)
1. Identify the Screen
Use list_screens or get_screen to find the correct projectId and
screenId.
2. Formulate the Edit Prompt
Apply the Prompt Enhancement Pipeline, focusing on specificity:
- Location: "Change the color of the [primary button] in the [hero section]..."
- Visuals: "...to a darker blue (#004080) and add a subtle shadow."
- Structure: "Add a secondary button next to the primary one with the text 'Learn More'."
3. Apply the Edit
Call the edit_screens tool.
{
"projectId": "...",
"selectedScreenIds": ["..."],
"prompt": "[Your targeted edit prompt]"
}
4. Present AI Feedback
Always show the text description and suggestions from outputComponents to the
user.
5. Download Design Assets
After editing, download the updated HTML and screenshot urls from
outputComponents to the .stitch/designs directory, overwriting previous
versions to ensure the local files reflect the latest edits.
- Naming: Use the screen ID or a descriptive slug for the filename.
- Tools: Use
curl -oviarun_commandor similar. - Directory: Ensure
.stitch/designsexists.
6. Update Project Metadata
After downloading assets, update .stitch/metadata.json to reflect any changes
(e.g., updated screen titles or new screen IDs from the edit). The metadata
file tracks all screens, their device types, and design system info. See the
manage-design-system skill's examples/metadata.json for the format.
7. Verify and Repeat
- Check the output screen to see if the changes were applied correctly.
- If more polish is needed, repeat the edit flow with a new specific prompt.
Generate Variants Flow (Explore Variations)
Use this flow when the user wants to explore alternative layouts, color schemes, or content variations of an existing screen.
1. Identify the Screen
Use list_screens or get_screen to find the correct projectId and
screenId.
2. Configure Variant Options
Call the generate_variants tool with the appropriate options:
{
"projectId": "...",
"selectedScreenIds": ["..."],
"prompt": "[Describe the direction for variants]",
"variantOptions": {
"variantCount": 3,
"creativeRange": "EXPLORE",
"aspects": ["LAYOUT", "COLOR_SCHEME"]
}
}
Variant Options:
variantCount: 1–5 variants (default: 3)creativeRange:REFINE(subtle),EXPLORE(balanced), orREIMAGINE(radical)aspects: Focus on specific dimensions —LAYOUT,COLOR_SCHEME,IMAGES,TEXT_FONT,TEXT_CONTENT, or leave empty for all
3. Present AI Feedback
Always show the text description and suggestions from outputComponents to the
user.
4. Download Design Assets
Download the variant HTML and screenshot urls from outputComponents to the
.stitch/designs directory.
- Naming: Use the screen ID or a descriptive slug for the filename.
- Tools: Use
curl -oviarun_commandor similar. - Directory: Ensure
.stitch/designsexists.
💡 Tips
- Be structural: Break the page down into header, hero, features, and footer in your prompt.
- Content first: Describe what each section contains (text, images, CTAs) rather than how it looks.
- Iterative Polish: Prefer editing for targeted adjustments over full re-generation.
- No theme leakage: Never put hex codes, font names, or color roles in a generation prompt — the design system handles all visual styling.
- Specify interactions: Mention hover states, animations, and click behavior rather than visual styling.
- Keep edits focused: One edit at a time is often better than a long list of changes.
- Reference components: Use professional terms like "navigation bar", "hero section", "footer", "card grid".
- Precise colors in edits: Use hex codes for exact color matching when editing existing screens.
📚 References
- Design Mappings — UI/UX keywords and atmosphere descriptors.
- Prompting Keywords — Technical terms Stitch understands best.
- Enhanced Prompt Example — Before/after prompt enhancement.
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.
