enhance-prompt
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.
What this skill does
# 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 (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:** ```markdown 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:** ```markdown 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
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.