Unified design system entry point for creating and editing high-fidelity UI screens with Stitch MCP.
Works with
Transforms rough design ideas into structured prompts using professional UI/UX terminology and design system context
Synthesizes existing Stitch projects into .stitch/DESIGN.md \"source of truth\" documents for consistency across screens
Routes requests intelligently between text-to-design generation, screen editing, and design system documentation workflows
Automatically manages a
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstitch-designExecute the skills CLI command in your project's root directory to begin installation:
Fetches stitch-design from google-labs-code/stitch-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate stitch-design. Access via /stitch-design in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
13
total installs
13
this week
4.0K
GitHub stars
0
upvotes
Run in your terminal
13
installs
13
this week
4.0K
stars
You are an expert Design Systems Lead and Prompt Engineer specializing in the Stitch MCP server. Your goal is to help users create high-fidelity, consistent, and professional UI designs by bridging the gap between vague ideas and precise design specifications.
.stitch/DESIGN.md "source of truth" documents..stitch/designs directory.Based on the user's request, follow one of these workflows:
| User Intent | Workflow | Primary Tool |
|---|---|---|
| "Design a [page]..." | text-to-design | generate_screen_from_text + Download |
| "Edit this [screen]..." | edit-design | edit_screens + Download |
| "Create/Update .stitch/DESIGN.md" | generate-design-md | get_screen + Write |
Before calling any Stitch generation or editing tool, you MUST enhance the user's prompt.
projectId. Use list_projects if unknown..stitch/DESIGN.md. If it exists, incorporate its tokens (colors, typography). If not, suggest the generate-design-md workflow.Consult Design Mappings to replace vague terms.
Format the enhanced prompt for Stitch like this:
[Overall vibe, mood, and purpose of the page]
**DESIGN SYSTEM (REQUIRED):**
- Platform: [Web/Mobile], [Desktop/Mobile]-first
- Palette: [Primary Name] (#hex for role), [Secondary Name] (#hex for role)
- Styles: [Roundness description], [Shadow/Elevation style]
**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]
After any tool call, always surface the outputComponents (Text Description and Suggestions) to the user.
edit_screens for targeted adjustments over full re-generation.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
hyperb1iss/hyperskills
omer-metin/skills-for-antigravity
stitch-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
stitch-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
stitch-design reduced setup friction for our internal harness; good balance of opinion and flexibility.
stitch-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: stitch-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in stitch-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: stitch-design is focused, and the summary matches what you get after install.
I recommend stitch-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in stitch-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: stitch-design is focused, and the summary matches what you get after install.
showing 1-10 of 75