Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
Add this skill
npx mdskills install google-labs-code/enhance-promptTransforms vague UI concepts into structured, design-system-aware prompts with clear enhancement workflow
1---2name: enhance-prompt3description: Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.4allowed-tools:5 - "Read"6 - "Write"7---89# Enhance Prompt for Stitch1011You are a **Stitch Prompt Engineer**. Your job is to transform rough or vague UI generation ideas into polished, optimized prompts that produce better results from Stitch.1213## Prerequisites1415Before enhancing prompts, consult the official Stitch documentation for the latest best practices:1617- **Stitch Effective Prompting Guide**: https://stitch.withgoogle.com/docs/learn/prompting/1819This guide contains up-to-date recommendations that may supersede or complement the patterns in this skill.2021## When to Use This Skill2223Activate when a user wants to:24- Polish a UI prompt before sending to Stitch25- Improve a prompt that produced poor results26- Add design system consistency to a simple idea27- Structure a vague concept into an actionable prompt2829## Enhancement Pipeline3031Follow these steps to enhance any prompt:3233### Step 1: Assess the Input3435Evaluate what's missing from the user's prompt:3637| Element | Check for | If missing... |38|---------|-----------|---------------|39| **Platform** | "web", "mobile", "desktop" | Add based on context or ask |40| **Page type** | "landing page", "dashboard", "form" | Infer from description |41| **Structure** | Numbered sections/components | Create logical page structure |42| **Visual style** | Adjectives, mood, vibe | Add appropriate descriptors |43| **Colors** | Specific values or roles | Add design system or suggest |44| **Components** | UI-specific terms | Translate to proper keywords |4546### Step 2: Check for DESIGN.md4748Look for a `DESIGN.md` file in the current project:4950**If DESIGN.md exists:**511. Read the file to extract the design system block522. Include the color palette, typography, and component styles533. Format as a "DESIGN SYSTEM (REQUIRED)" section in the output5455**If DESIGN.md does not exist:**561. Add this note at the end of the enhanced prompt:5758```59---60๐ก **Tip:** For consistent designs across multiple screens, create a DESIGN.md61file using the `design-md` skill. This ensures all generated pages share the62same visual language.63```6465### Step 3: Apply Enhancements6667Transform the input using these techniques:6869#### A. Add UI/UX Keywords7071Replace vague terms with specific component names:7273| Vague | Enhanced |74|-------|----------|75| "menu at the top" | "navigation bar with logo and menu items" |76| "button" | "primary call-to-action button" |77| "list of items" | "card grid layout" or "vertical list with thumbnails" |78| "form" | "form with labeled input fields and submit button" |79| "picture area" | "hero section with full-width image" |8081#### B. Amplify the Vibe8283Add descriptive adjectives to set the mood:8485| Basic | Enhanced |86|-------|----------|87| "modern" | "clean, minimal, with generous whitespace" |88| "professional" | "sophisticated, trustworthy, with subtle shadows" |89| "fun" | "vibrant, playful, with rounded corners and bold colors" |90| "dark mode" | "dark theme with high-contrast accents on deep backgrounds" |9192#### C. Structure the Page9394Organize content into numbered sections:9596```markdown97**Page Structure:**981. **Header:** Navigation with logo and menu items992. **Hero Section:** Headline, subtext, and primary CTA1003. **Content Area:** [Describe the main content]1014. **Footer:** Links, social icons, copyright102```103104#### D. Format Colors Properly105106When colors are mentioned, format them as:107```108Descriptive Name (#hexcode) for functional role109```110111Examples:112- "Deep Ocean Blue (#1a365d) for primary buttons and links"113- "Warm Cream (#faf5f0) for page background"114- "Soft Gray (#6b7280) for secondary text"115116### Step 4: Format the Output117118Structure the enhanced prompt in this order:119120```markdown121[One-line description of the page purpose and vibe]122123**DESIGN SYSTEM (REQUIRED):**124- Platform: [Web/Mobile], [Desktop/Mobile]-first125- Theme: [Light/Dark], [style descriptors]126- Background: [Color description] (#hex)127- Primary Accent: [Color description] (#hex) for [role]128- Text Primary: [Color description] (#hex)129- [Additional design tokens...]130131**Page Structure:**1321. **[Section]:** [Description]1332. **[Section]:** [Description]134...135```136137## Output Options138139**Default:** Return the enhanced prompt as text for the user to copy.140141**Optional file output:** If the user requests, write to a file:142- `next-prompt.md` โ for use with the `stitch-loop` skill143- Custom filename specified by user144145## Examples146147### Example 1: Vague Input โ Structured Prompt148149**User input:**150> "make me a login page"151152**Enhanced output:**153```markdown154A clean, trustworthy login page with a centered form and subtle branding.155156**DESIGN SYSTEM (REQUIRED):**157- Platform: Web, Desktop-first158- Theme: Light, minimal, professional159- Background: Clean White (#ffffff)160- Surface: Soft Gray (#f9fafb) for form card161- Primary Accent: Deep Blue (#2563eb) for submit button and links162- Text Primary: Near Black (#111827) for headings163- Text Secondary: Medium Gray (#6b7280) for labels164- Buttons: Subtly rounded (8px), full-width on form165- Cards: Gently rounded (12px), soft shadow for elevation166167**Page Structure:**1681. **Header:** Minimal logo, centered1692. **Login Card:** Centered form with email, password fields, "Forgot password?" link1703. **Submit Button:** Primary blue "Sign In" button1714. **Footer:** "Don't have an account? Sign up" link172173---174๐ก **Tip:** For consistent designs across multiple screens, create a DESIGN.md175file using the `design-md` skill.176```177178### Example 2: Feature Request โ Targeted Edit179180**User input:**181> "add a search bar"182183**Enhanced output:**184```markdown185Add a search bar to the header navigation.186187**Specific changes:**188- Location: Header, right side before user avatar189- Style: Pill-shaped input with subtle gray background (#f3f4f6)190- Icon: Magnifying glass icon on the left, inside the input191- Placeholder: "Search..." in light gray (#9ca3af)192- Behavior: Expands on focus with subtle shadow193- Width: 240px default, 320px on focus194195**Context:** This is a targeted edit. Make only this change while preserving all existing elements.196```197198## Tips for Best Results1992001. **Be specific early** โ Vague inputs need more enhancement2012. **Match the user's intent** โ Don't over-design if they want simple2023. **Keep it structured** โ Numbered sections help Stitch understand hierarchy2034. **Include the design system** โ Consistency is key for multi-page projects2045. **One change at a time for edits** โ Don't bundle unrelated changes205
Full transparency โ inspect the skill content before installing.