agentleFS
BAKUGOS1BAKUGOS1/SkilledAgents-Toolkit/skills/codex/enhance-prompt/SKILL.md

enhance-prompt

Skill0 starsChanged 5 months agoMITView on GitHub

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.

20 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 15
  2. Distinctive:

    Add design system consistency to a simple idea

    line 26
  3. Distinctive:

    Follow these steps to enhance any prompt:

    line 31
  4. Very specific:

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

    line 48
  5. Distinctive:

    Read the file to extract the design system block

    line 51
  6. Distinctive:

    Add this note at the end of the enhanced prompt:

    line 56
  7. Distinctive:

    Add descriptive adjectives to set the mood:

    line 83
  8. Distinctive:

    When colors are mentioned, format them as:

    line 106
  9. Distinctive:

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

    line 141

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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:

ElementCheck forIf missing...
Platform"web", "mobile", "desktop"Add based on context or ask
Page type"landing page", "dashboard", "form"Infer from description
StructureNumbered sections/componentsCreate logical page structure
Visual styleAdjectives, mood, vibeAdd appropriate descriptors
ColorsSpecific values or rolesAdd design system or suggest
ComponentsUI-specific termsTranslate 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:

VagueEnhanced
"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:

BasicEnhanced
"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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.