enhance-prompt

google-labs-code/stitch-skills · updated May 27, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/google-labs-code/stitch-skills --skill enhance-prompt
0 commentsdiscussion
summary

Transforms vague UI ideas into polished, Stitch-optimized prompts with design system context.

  • Assesses missing elements (platform, page type, visual style, colors, components) and fills gaps systematically
  • Checks for and integrates DESIGN.md files to ensure consistency across multi-page projects
  • Applies enhancement techniques including UI/UX keyword specificity, mood amplification, page structure organization, and proper color formatting
  • Outputs structured prompts ready for Stitch
skill.md

Enhance Prompt for Stitch

You 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.

Prerequisites

Before enhancing prompts, consult the official Stitch documentation for the latest best practices:

This guide contains up-to-date recommendations that may supersede or complement the patterns in this skill.

When to Use This Skill

Activate when a user wants to:

  • Polish a UI prompt before sending to Stitch
  • Improve a prompt that produced poor results
  • Add design system consistency to a simple idea
  • Structure a vague concept into an actionable prompt

Enhancement Pipeline

Follow these steps to enhance any prompt:

Step 1: Assess the Input

Evaluate what's missing from the user's prompt:

Element Check for If missing...
Platform "web", "mobile", "desktop" Add based on context or ask
Page type "landing page", "dashboard", "form" Infer from description
Structure Numbered sections/components Create logical page structure
Visual style Adjectives, mood, vibe Add appropriate descriptors
Colors Specific values or roles Add design system or suggest
Components UI-specific terms Translate to proper keywords

Step 2: Check for DESIGN.md

Look for a DESIGN.md file in the current project:

If DESIGN.md exists:

  1. Read the file to extract the design system block
  2. Include the color palette, typography, and component styles
  3. Format as a "DESIGN SYSTEM (REQUIRED)" section in the output

If DESIGN.md does not exist:

  1. Add this note at the end of the enhanced prompt:
---
💡 **Tip:** For consistent designs across multiple screens, create a DESIGN.md 
file using the `design-md` skill. This ensures all generated pages share the 
same visual language.

Step 3: Apply Enhancements

Transform the input using these techniques:

A. Add UI/UX Keywords

Replace vague terms with specific component names:

Vague Enhanced
"menu at the top" "navigation bar with logo and menu items"
"button" "primary call-to-action button"
"list of items" "card grid layout" or "vertical list with thumbnails"
"form" "form with labeled input fields and submit button"
"picture area" "hero section with full-width image"

B. Amplify the Vibe

Add descriptive adjectives to set the mood:

Basic Enhanced
"modern" "clean, minimal, with generous whitespace"
"professional" "sophisticated, trustworthy, with subtle shadows"
"fun" "vibrant, playful, with rounded corners and bold colors"
"dark mode" "dark theme with high-contrast accents on deep backgrounds"

C. Structure the Page

Organize content into numbered sections:

**Page Structure:**
1. **Header:** Navigation with logo and menu items
2. **Hero Section:** Headline, subtext, and primary CTA
3. **Content Area:** [Describe the main content]
4. **Footer:** Links, social icons, copyright

D. Format Colors Properly

When colors are mentioned, format them as:

Descriptive Name (#hexcode) for functional role

Examples:

  • "Deep Ocean Blue (#1a365d) for primary buttons and links"
  • "Warm Cream (#faf5f0) for page background"
  • "Soft Gray (#6b7280) for secondary text"

Step 4: Format the Output

Structure the enhanced prompt in this order:

[One-line description of the page purpose and vibe]

**DESIGN SYSTEM (REQUIRED):**
- Platform: [Web/Mobile], [Desktop/Mobile]-first
- Theme: [Light/Dark], [style descriptors]
- Background: [Color description] (#hex)
- Primary Accent: [Color description] (#hex) for [role]
- Text Primary: [Color description] (#hex)
- [Additional design tokens...]

**Page Structure:**
1. **[Section]:** [Description]
2. **[Section]:** [Description]
...

Output Options

Default: Return the enhanced prompt as text for the user to copy.

Optional file output: If the user requests, write to a file:

  • next-prompt.md — for use with the stitch-loop skill
  • Custom filename specified by user

Examples

Example 1: Vague Input → Structured Prompt

User input:

"make me a login page"

Enhanced output:

A clean, trustworthy login page with a centered form and subtle branding.

**DESIGN SYSTEM (REQUIRED):**
- Platform: Web, Desktop-first
- Theme: Light, minimal, professional
- Background: Clean White (#ffffff)
- Surface: Soft Gray (#f9fafb) for form card
- Primary Accent: Deep Blue (#2563eb) for submit button and links
- Text Primary: Near Black (#111827) for headings
- Text Secondary: Medium Gray (#6b7280) for labels
- Buttons: Subtly rounded (8px), full-width on form
- Cards: Gently rounded (12px), soft shadow for elevation

**Page Structure:**
1. **Header:** Minimal logo, centered
2. **Login Card:** Centered form with email, password fields, "Forgot password?" link
3. **Submit Button:** Primary blue "Sign In" button
4. **Footer:** "Don't have an account? Sign up" link

---
💡 **Tip:** For consistent designs across multiple screens, create a DESIGN.md 
file using the `design-md` skill.

Example 2: Feature Request → Targeted Edit

User input:

"add a search bar"

Enhanced output:

Add a search bar to the header navigation.

**Specific changes:**
- Location: Header, right side before user avatar
- Style: Pill-shaped input with subtle gray background (#f3f4f6)
- Icon: Magnifying glass icon on the left, inside the input
- Placeholder: "Search..." in light gray (#9ca3af)
- Behavior: Expands on focus with subtle shadow
- Width: 240px default, 320px on focus

**Context:** This is a targeted edit. Make only this change while preserving all existing elements.

Tips for Best Results

  1. Be specific early — Vague inputs need more enhancement
  2. Match the user's intent — Don't over-design if they want simple
  3. Keep it structured — Numbered sections help Stitch understand hierarchy
  4. Include the design system — Consistency is key for multi-page projects
  5. One change at a time for edits — Don't bundle unrelated changes
how to use enhance-prompt

How to use enhance-prompt on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add enhance-prompt
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/google-labs-code/stitch-skills --skill enhance-prompt

The skills CLI fetches enhance-prompt from GitHub repository google-labs-code/stitch-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/enhance-prompt

Reload or restart Cursor to activate enhance-prompt. Access the skill through slash commands (e.g., /enhance-prompt) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.565 reviews
  • Sofia Patel· Dec 20, 2024

    enhance-prompt has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Liam Flores· Dec 20, 2024

    Solid pick for teams standardizing on skills: enhance-prompt is focused, and the summary matches what you get after install.

  • James Gill· Dec 16, 2024

    Keeps context tight: enhance-prompt is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Charlotte Mehta· Nov 11, 2024

    I recommend enhance-prompt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sofia Park· Nov 7, 2024

    enhance-prompt is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Charlotte Park· Oct 26, 2024

    Solid pick for teams standardizing on skills: enhance-prompt is focused, and the summary matches what you get after install.

  • Fatima Tandon· Oct 2, 2024

    Keeps context tight: enhance-prompt is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sofia Choi· Sep 25, 2024

    Registry listing for enhance-prompt matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Emma Rahman· Sep 21, 2024

    enhance-prompt has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Luis Chen· Sep 17, 2024

    enhance-prompt reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 65

1 / 7