Transform Rough Ideas into Optimized Stitch UI Prompts

Enhance Prompt for Stitch turns a rough or vague UI-generation idea into a polished, structured prompt tuned for Google's Stitch tool. It first assesses what's missing from the input against six checks - platform, page type, structure, visual style, colors, and named components - inferring or asking for whatever isn't there. It checks the current project for a DESIGN.md file: if one exists, it pulls the color palette, typography, and component styles into a required "DESIGN SYSTEM" section; if not, it appends a tip suggesting the user create one with the design-md skill for consistency across screens. It then applies four enhancement techniques: replacing vague terms with specific component names, for example "menu at the top" becomes "navigation bar with logo and menu items"; amplifying mood with concrete descriptors, for example "modern" becomes "clean, minimal, with generous whitespace"; organizing content into a numbered page structure - header, hero, content, footer; and formatting any mentioned colors as a descriptive name plus hex code and functional role, for example "Deep Ocean Blue (#1a365d) for primary buttons and links." The final output follows a fixed order - a one-line purpose and vibe description, the required design-system block, and the numbered page structure - returned as text by default, or written to next-prompt.md, for chaining into the stitch-loop skill, or a custom filename if the user asks. It also handles targeted edits differently from full-page prompts: "add a search bar" becomes a scoped change description covering location, style, behavior, and sizing, with an explicit instruction to preserve everything else.

Activate it when a user wants to polish a UI prompt before sending it to Stitch, improve a prompt that produced poor results, add design-system consistency to a simple idea, or structure a vague concept into an actionable prompt. It defers to Stitch's own official prompting guide for the latest best practices, since those may supersede or complement what's encoded here. Its stated tips: be specific early since vague inputs need more enhancement, match the user's actual intent rather than over-designing a simple request, keep structure numbered so Stitch can parse hierarchy, and bundle only one change at a time for targeted edits rather than mixing unrelated changes.

Input: a rough UI idea or edit request, plus an optional project DESIGN.md file. Output: an enhanced prompt with a one-line description, a required design-system block (platform, theme, colors with hex codes, typography and style tokens), and a numbered page structure, or, for a targeted edit, a scoped change description, returned as text or written to a file.

• Google Stitch's official prompting guide at stitch.withgoogle.com/docs/learn/prompting
• DESIGN.md project file for design-system consistency, created by the related design-md skill
• next-prompt.md output file for chaining into the stitch-loop skill

Anyone writing UI-generation prompts for Stitch who wants consistent, structured, design-system-aware prompts instead of vague one-liners that produce inconsistent results.