enhance-prompt
by google-labs-codeThe enhance-prompt skill turns vague UI ideas into clearer, Stitch-ready prompts with stronger structure, UI/UX vocabulary, and design-system context. Use this enhance-prompt guide to improve prompt specificity, reduce guesswork, and get more consistent results for prompt writing and UI generation.
This skill scores 76/100, which means it is a solid but not exceptional listing candidate for directory users. It clearly helps agents turn vague UI ideas into Stitch-optimized prompts, and the repository includes enough workflow detail and reference material to make install decisions credible, though users should expect some reliance on external Stitch docs and a few placeholder-like gaps.
- Clear activation and use cases for prompt enhancement before Stitch generation.
- Substantial workflow guidance with a step-by-step enhancement pipeline and supporting UI/UX keyword reference.
- Install decision value is strong: the skill is self-contained, has valid frontmatter, and includes an install command plus examples.
- It points users to external Stitch documentation for the latest best practices, so some core behavior depends on outside guidance.
- No scripts or rules files are present, and the references appear more vocabulary-driven than deeply operational for edge cases.
Overview of enhance-prompt skill
The enhance-prompt skill helps turn a rough UI idea into a stronger, Stitch-ready prompt with better structure, clearer intent, and more relevant UI language. It is most useful for people who already know what they want roughly, but need help converting that into a prompt that produces cleaner layout, better component choices, and more consistent design direction.
What enhance-prompt is for
Use the enhance-prompt skill when your starting point is too vague for reliable generation, such as “make a login page” or “build a dashboard for analytics.” The skill adds missing context like page type, component structure, visual tone, and design-system hints so the model has less room to guess.
Who gets the most value
This enhance-prompt guide is best for Stitch users, prompt writers, and teams that want repeatable UI generation without writing every detail manually. It is especially helpful when you want faster first drafts, fewer weak outputs, or prompts that align better with an existing design system.
What makes it different
The enhance-prompt skill is not just prompt polishing. It follows an enhancement pipeline: assess what is missing, add UI/UX vocabulary, check for design-system context, and format the result so Stitch can act on it more predictably. That makes it more practical than a generic “rewrite this better” prompt.
How to Use enhance-prompt skill
Install and activate it
Use the repo install flow from the project README: npx skills add google-labs-code/stitch-skills --skill enhance-prompt --global. If you are working inside a skills-enabled environment, activate enhance-prompt before asking for a rewrite so the model applies the skill’s workflow instead of improvising a generic prompt edit.
Give the skill a usable starting point
The enhance-prompt skill works best when you provide the raw idea, target surface, and any constraints you already know. Strong inputs look like this:
- “Enhance this prompt for a mobile onboarding flow with 3 steps, friendly tone, and brand colors already defined.”
- “Improve this prompt for a B2B analytics dashboard with sidebar navigation and dense information hierarchy.”
- “Rewrite this vague login-page prompt for Stitch, keeping it minimal and accessible.”
If you only send a theme, the skill has to infer too much. If you provide platform, page type, audience, and any design system rules, the output is much more usable.
Read these files first
Start with SKILL.md for the workflow, then check README.md for install and usage context. The most valuable reference file is references/KEYWORDS.md, which gives the component and adjective vocabulary the skill uses to enrich prompts. If you are adapting the skill to your own repo, scan the whole tree for any design-system or rule files before you copy the pattern.
Shape your request for better output
A good enhance-prompt usage request should tell the skill what kind of UI to generate, what tone to keep, and what must not change. For example, say whether the result should be “clean and enterprise,” “playful and colorful,” or “premium and restrained.” Also mention constraints like responsive behavior, accessibility, or reuse of an existing design system. That lets enhance-prompt add useful detail instead of generic filler.
enhance-prompt skill FAQ
Is enhance-prompt only for Stitch prompts?
Yes, the skill is tuned for Stitch prompt writing and prompt cleanup. If your goal is a general marketing prompt, a coding prompt, or a research prompt, this is probably the wrong tool. The strength of enhance-prompt is that it adds the kinds of UI details Stitch benefits from most.
Do I need prompt-writing experience?
No. The enhance-prompt skill is useful even for beginners because it can turn a short idea into a more complete brief. You will get better results if you can name the platform, page type, and style goal, but you do not need to know UI jargon well to start.
How is this better than asking an AI to “improve my prompt”?
A generic rewrite often makes text sound nicer without improving design specificity. The enhance-prompt skill adds practical UI structure, terminology from references/KEYWORDS.md, and a design-system check, which makes the final prompt more actionable for Stitch.
When should I not use it?
Do not use enhance-prompt if you already have a highly detailed, production-ready prompt or if your task is not UI generation. It is also less useful when you want strict copy editing only, because its job is to improve prompt quality for design output, not to rewrite prose for style alone.
How to Improve enhance-prompt skill
Feed it the constraints that matter
The biggest quality gains come from specifying what the UI must support: key user goal, page type, device target, and any brand rules. Instead of “make a dashboard,” try “make a desktop dashboard for sales managers with clear hierarchy, compact cards, and a trustable enterprise feel.” That gives enhance-prompt enough structure to choose better components and tone.
Use the reference vocabulary intentionally
The references/KEYWORDS.md file is there to reduce guesswork. If you know the layout should include tabs, a sidebar, alerts, or a card grid, say so. If you want a specific mood, name it directly. The more the input aligns with the reference vocabulary, the less likely the enhanced prompt will drift into vague UI language.
Watch for the common failure mode
The main failure mode is over-inference: the prompt becomes detailed but not faithful to the original intent. Prevent that by telling the skill what must stay fixed, what can be invented, and what should remain minimal. If the first result is too broad, tighten the brief; if it is too narrow, add product context and audience detail.
Iterate from the first output
Treat the first enhanced prompt as a draft, then refine based on what Stitch actually produces. If the output is too plain, ask enhance-prompt to add stronger visual direction. If it is too busy, ask it to reduce component density and simplify hierarchy. For best results, improve the source brief before asking for another rewrite instead of repeatedly polishing the same weak input.