
Enhance Prompt
Turn vague UI ideas into Stitch-ready prompts with platform, page type, design-system context, and UX keywords before you generate screens.
Overview
Enhance Prompt is an agent skill for the Build phase that transforms vague UI ideas into polished, Stitch-optimized generation prompts.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill enhance-promptWhat is this skill?
- 4-step enhancement pipeline: assess input, add specificity, inject design system, structure for Stitch
- Input audit table for platform, page type, and numbered sections when missing
- Stitch-optimized wording aligned with Google Stitch prompting docs
- Polish flows for poor generations and vague concepts
- Frontmatter tools: Read and Write for saving enhanced prompts
- 4-step enhancement pipeline with input assessment table
Adoption & trust: 1 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
Your Stitch prompt is too vague and keeps producing weak layouts, missing platform context or design-system consistency.
Who is it for?
Solo builders using Stitch for landing pages, dashboards, or mobile UI mocks before coding the frontend.
Skip if: Backend API design, non-Stitch image tools, or teams that already maintain a locked design spec with no iteration on prompts.
When should I use this skill?
User wants to polish a UI prompt before Stitch, improve poor Stitch results, add design system consistency, or structure a vague UI concept.
What do I get? / Deliverables
You get a structured, keyword-rich Stitch prompt with platform and page type filled in, ready to paste into generation.
- Stitch-optimized structured UI generation prompt
- Gap-filled platform and page-type specification
Recommended Skills
Journey fit
Build → frontend is where UI generation prompts are authored before implementation or handoff to code. Frontend subphase covers landing pages, dashboards, and forms—the exact page types the enhancement pipeline infers and structures.
How it compares
A prompt-polishing skill for Stitch UI generation, not a component library or Figma-to-code integration.
Common Questions / FAQ
Who is enhance-prompt for?
Indie frontend builders and designers who generate UI with Google Stitch and want agent help tightening prompts before each run.
When should I use enhance-prompt?
In the build frontend phase when polishing a prompt before Stitch, fixing a bad generation, or structuring a vague UI concept into sections.
Is enhance-prompt safe to install?
It declares Read/Write tooling; review the Security Audits panel on this Prism page and restrict write paths in your agent config.
SKILL.md
READMESKILL.md - Enhance Prompt
# 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: - **Stitch Effective Prompting Guide**: https://stitch.withgoogle.com/docs/learn/prompting/ 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: ```markdown **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: ```markdown [One-line description of the page purpose and vibe] **DESIGN SYSTEM (RE