SKILL.md
$27
User Intent
Workflow
Primary Tool
"Design a [page]..."
generate_screen_from_text + Download
"Edit this [screen]..."
edit_screens + Download
"Create/Update .stitch/DESIGN.md"
get_screen + Write
🎨 Prompt Enhancement Pipeline
Before calling any Stitch generation or editing tool, you MUST enhance the user's prompt.
1. Analyze Context
- Project Scope: Maintain the current
projectId. Uselist_projectsif unknown.
- Design System: Check for
.stitch/DESIGN.md. If it exists, incorporate its tokens (colors, typography). If not, suggest thegenerate-design-mdworkflow.
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"
3. Structure the Final Prompt
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]4. Present AI Insights
After any tool call, always surface the outputComponents (Text Description and Suggestions) to the user.
📚 References
- Tool Schemas — How to call Stitch MCP tools.
- Design Mappings — UI/UX keywords and atmosphere descriptors.
- Prompting Keywords — Technical terms Stitch understands best.
💡 Best Practices
- Iterative Polish: Prefere
edit_screensfor targeted adjustments over full re-generation.
- Semantic First: Name colors by their role (e.g., "Primary Action") as well as their appearance.
- Atmosphere Matters: Explicitly set the "vibe" (Minimalist, Vibrant, Brutalist) to guide the generator.